Each tab provides options for a specific configuration. Depending on what you want to monitor, you must specify values in the respective tabs.
The following table lists the tabs and the configurations that you can do in them:
Tab | Supported Configuration |
---|
Monitoring | To add and configure monitor types for the compatible PATROL monitoring solutions that are located in the deployable packages. |
Filtering | To control the data and events that are sent to the Infrastructure Management server from the PATROL Agents. |
Polling Intervals | To configure the time interval between two consecutive data polls. |
Agent Thresholds | To configure intelligent thresholds for attributes of a monitor type on the PATROL Agents. |
Server Thresholds | To configure thresholds for the monitor instances on the Infrastructure Management server. |
Agent | To configure the properties of a PATROL Agent and specify the action that the Agent must perform when the policy is applied. |
Server | To specify actions to be performed on the Infrastructure Management server when the policy that is created, is applied |
Configuration Variables | To control the PATROL Agent configuration by defining values for the Agent's configuration variables. |
You can add and configure monitor types for the compatible PATROL monitoring solutions that are located in the Deployable Package Repository. For a list of monitoring solutions and monitor types that you can configure, see Monitoring Solutions and KMs . To configure custom monitoring solutions, ensure the solution is structured correctly; for details, see Developing a PATROL Knowledge Module .
Ensure that the Monitoring tab is selected. By default, this tab is selected. If not, click it.
Click New Monitor Configuration.
In the Add Monitor Configuration dialog box, configure the following properties:
Property |
Description |
Monitoring Solution |
Name of the monitoring solution. A solution can have many Knowledge Modules (KMs) under it. |
Version |
Version of the selected monitoring solution |
Monitor Profile |
Name of the monitor profile to which the monitor types that you want to enable are associated.
Each solution contains multiple monitoring profiles that help to reduce unnecessary monitoring. Each monitoring profile is associated with a group of monitor types. If a profile has monitor types that require you to enter information, they are listed in the Monitor type list, and you can configure them. If the profile has no monitor types that require input, all the monitor types are enabled by default and the Monitor Type list is disabled. To view all the monitor types that belong to a selected profile, click the Click to view Monitor Types option.
The monitor types that belong to a profile are pre-determined. You cannot add or remove them from a profile.
|
Monitor Type |
Name of the monitor type that you want to configure. You can select one from the list:
For documentation or more information, click the Help icon next to the list. The online documentation for that monitor type is displayed. |
- Click OK. The configured monitor type is added as a new row in the Monitoring page.
- To continue adding configuration details, repeat the previous steps for a different monitor type, version, profile, or solution.
- To modify a monitor configuration, click the action menu for that configuration and select Edit. Modify the configuration and click OK.
- To delete a monitor configuration, click the action menu for that configuration and select Delete. After you save the policy, the deleted monitor type configuration is removed from the selected PATROL Agents.
After you save or update a policy, the monitor type configurations are pushed to the selected PATROL Agents.
Back to top
After you configure the monitor types in the PATROL Agents, they send the collected data and the generated events to the Infrastructure Management server. You can configure filters to control the data and events that are sent to the Infrastructure Management server per parameter.
You can filter the data either from a specific Agent or from a specific monitor type. The supported filtering options are as follows:
- Send events only
- Send trended performance data only
- Send trended performance data and events
- Send no trended performance data and no events
Specify the time interval between two consecutive data polls. You need to specify a separate poll interval for every parameter.
- Click the Polling Intervals tab.
- Add a polling interval:
- Click Add Polling Interval.
Select values for the following options:
- Monitoring Solution - Version - Monitor Type - Parameter - Parameter Polling Interval
|
- Click OK. The polling interval is added to the table in the Polling Interval page.
- To add more polling intervals, repeat the previous step.
- To modify the properties of a polling interval: Click the action menu associated with that polling interval, and select Edit.
- To delete a polling interval: Click the action menu associated with that polling interval and select Delete.
Back to top
Define thresholds on PATROL Agents
Configure range-based thresholds for attributes of a monitor type on the PATROL Agents. You can specify whether the thresholds apply to a monitor type or to an instance of a monitor type.
- Click the Agent Threshold tab.
Click Add Agent Threshold.
Specify values for the following properties:
Property |
Description |
Monitoring Solution |
Monitoring solution |
Version |
Version of the monitoring solution |
Monitor Type |
Monitor type |
|
Monitoring Scope |
Scope of the threshold. Select one of the following options:
- All Instances of the Monitor Type: The threshold applies to the monitor type.
Monitor Instances: The threshold applies to a specific instance of the monitor type. To identify the instance, specify the instance ID in the SID box.
Click here to know the steps to determine the SID of a monitoring instance
- Log on to BMC TrueSight Infrastructure Management Operator console.
- In the navigation pane, select Devices > Grid View.
- Click any device.
The Show Monitors page is displayed.
- Hover the mouse over the specific monitor instance, and the tool tip displays the SID for the instance.
- Note down the SID. You can use the SID value when you configure the agent threshold.
If you want to specify multiple SIDs, you can use regular expressions to search for multiple matching instance SIDs. If you use regular expressions to search for the matching instance SIDs, ensure that you have selected Is a Regular Expression.
Click here to view the supported characters for regular expressions
Character |
Expression |
Description |
^ |
Beginning of line |
Only finds the search term if the term is at the beginning of a line |
$ |
End of line |
Only finds the search term if the term is at the end of a line |
. |
Any character |
Matches any single character except a line break |
* |
Zero or more |
Matches zero or more occurrences of the preceding expression, making all possible matches |
[] |
Any one character in the set |
Matches any one of the characters within the []. To specify a range of characters, list the starting and ending characters, separated by a dash (-), as in [a-z]. |
[^] |
Any one character not in the set |
Matches any character not in the set of characters following the ^ |
\< |
Beginning of word |
Matches only when a word begins at this point in the text |
\> |
End of word |
Matches only when a word ends at this point in the text |
|
Monitoring Attribute |
Monitoring attribute Important: Some monitoring attributes are designated as key performance indicators (KPIs). Depending on the monitored environment and version, the list of KPIs might appear differently in the Operator console.
|
Threshold Ranges: Configure border and threshold ranges for the selected monitoring attribute. |
For Border Thresholds, Threshold 1, and Threshold 2: |
Enable |
Select this check box for the type of threshold that you want to configure. |
Min, Max |
Minimum and maximum values for the range.
|
Select Event Severity |
Severity type to be associated with the event. Select one of the following options:
When the configured threshold is violated, the triggered event is of the selected severity.
|
Trigger an Event |
Condition to trigger an event. Select one of the following options:
- Immediately on threshold violation: Triggers an event immediately after a threshold violation.
- After threshold violation occurs N times: Triggers an event after the threshold is violated after the specified (N) number of times. Ensure that you specify a value greater than 0 in the N box.
- After all auto-recovery actions fail: Triggers an event after the recovery actions that are configured at the PATROL Agent fail.
|
- Click OK. The threshold is added to the table on the Agent Threshold page.
Back to top
Create server-level thresholds
You can create thresholds for the monitor instances on the Infrastructure Management server. For information about the types of thresholds, see Thresholds, KPIs, and baselines.
To configure the server thresholds:
- Click the Server Threshold tab.
- Click Add Server Threshold.
Specify values for the following properties:
Option |
Description |
Monitoring Solution |
Name of the monitoring solution. A solution can have many Knowledge Modules (KMs) under it. |
Version |
Version of the monitoring solution. |
Monitor Type |
A list of monitor types for the selected solution. |
Monitor Instance Name
|
Name of the monitor instance. Depending on your requirement, specify the monitor instance information in one of the following formats: - Name of the monitor instance - A regular expression that can match multiple instances.
Click here to view the supported characters for regular expressions
Character |
Expression |
Description |
^ |
Beginning of line |
Only finds the search term if the term is at the beginning of a line |
$ |
End of line |
Only finds the search term if the term is at the end of a line |
. |
Any character |
Matches any single character except a line break |
* |
Zero or more |
Matches zero or more occurrences of the preceding expression, making all possible matches |
[] |
Any one character in the set |
Matches any one of the characters within the []. To specify a range of characters, list the starting and ending characters, separated by a dash (-), as in [a-z]. |
[^] |
Any one character not in the set |
Matches any character not in the set of characters following the ^ |
\< |
Beginning of word |
Matches only when a word begins at this point in the text |
\> |
End of word |
Matches only when a word ends at this point in the text |
- Name of a monitor instance with the associated device in the following format: deviceName/instanceName. Also, select the Associate with a Device check box. |
Monitoring Attribute |
|
Threshold: Configure the threshold parameters for the threshold type that you have selected. You can select either of the following types: Absolute, Signature, and Abnormality.
|
Threshold types |
Parameter |
Description |
Absolute, Signature |
Severity |
Severity type to be associated with the event. Select one of the following options:
When the configured threshold is breached, the triggered event is of the selected severity.
|
Absolute, Signature, Abnormality |
Duration |
The length of time, in minutes, that the data values must breach the threshold, before an event is generated. For example, you could specify that the attribute data value must remain above the baseline for 10 minutes before an event is generated. By specifying this parameter, you can reduce the number of events generated by an absolute threshold. |
Threshold Value
|
An absolute value that is above and beyond the baseline value. If you set a threshold, an abnormality will be generated only when it violates both the set baseline and the threshold value. |
Outside Baseline Type |
Type of baseline. Select one of the following options: Not Enabled Auto Hourly Daily Weekly Hourly and Daily All
By selecting a baseline type to combine with the absolute threshold, you can ensure that an event is not generated unless the data value breaches both the threshold value AND the selected baseline (Hourly, Daily, Weekly, Daily and Hourly, or All baselines). Thereby, you can reduce the number of events generated by an absolute threshold. |
Absolute |
Comparison
|
A comparison operator to specify when a breach occurs. You can specify when the data value is greater than, less than, greater than or equal to, less than or equal to, or equal to the specified threshold value. |
Absolute |
Generate Predictive Event |
Select the check box if you want an early-warning predictive event to be generated 2-3 hours before the absolute threshold is breached. This enables you to get some lead time to take an action, if required. |
Absolute |
Auto Close Events
|
Select the check box to specify that the events generated by a breach of the threshold be automatically closed if the data values that are collected are not breaching the threshold anymore. If you do not select this option, you can manually close such events in the TrueSight console. |
Signature, Abnormality |
Above/Below Threshold |
Select Above or Below depending on whether the collected data values must be above or below a baseline before an event is generated. |
Minimum Sampling Window |
The number of data points that must be collected or the amount of time that must pass (depending on the attribute) before an event is generated. At least five data points are required before an event is generated for any threshold type. If your minimum sampling window is set too small to allow at least 5 data points, then Infrastructure Management will wait until five data points have been collected before generating the event, regardless of the value entered into the sampling window. Example for abnormality threshold: If you set a minimum sampling window to 10 minutes on a specific monitor attribute but the polling rate of that monitor is 5 minutes, 25 minutes must pass before an abnormality is generated. For this reason, BMC recommends to use lower polling rates for monitors. |
Absolute Deviation (%)
|
An absolute number above or below a baseline that the collected data values must reach before an event is generated. Example for abnormality threshold: For example, if you set a daily abnormality threshold for the Total Number of Disk I/O Request attribute for the VMware Disk Performance monitor type, and you set the absolute deviation to 3, then an abnormality event would not be generated until the Daily baseline for the total number of VMware disk I/O requests plus three additional requests had been made. If the Daily baseline for VMware disk I/O requests was 45, then an abnormality event would be generated when 48 VMware disk I/O requests were made. |
Percent Deviation (%) |
The percent of the baseline above or below the baseline that the collected data values must reach before an event is generated. Example for abnormality threshold: If you set a hourly abnormality threshold for for the Average Disk Throughput attribute for the VMware Disk Performance monitor type, and you set the percentage deviation to 10, then an abnormality event would not be generated until the value of the data collected reached the Hourly baseline for the average VMware disk throughput plus an additional 10 percent of the baseline value. If the Hourly baseline for average VMware disk throughput was 2500 KB per second, then an abnormality event would be generated when the VMware disk throughput became 2750 KB per second |
|
- Click OK.
- To modify parameters of a threshold, click the action menu for that threshold and select Edit.
- To remove a threshold, click the action menu for that threshold and select Delete. After you save the policy, the deleted threshold configurations are removed from the selected PATROL Agents.
After you save or update a policy, the new threshold configurations are pushed to the selected PATROL Agents.
Back to top
You can configure the properties of a PATROL Agent and specify the action that the Agent must perform when the policy is applied.
For more information, see Specifying objects in an authorization profile .
Click the Agent tab.
Specify the following properties:
Property |
Description |
Agent Default Account |
User Name |
The user name that you want to use to run the PATROL Agent. The user name must have access permissions to the PATROL Agent directory.
|
Password |
Password for the specified user name |
Confirm Password |
Password for the specified user name |
Restart Agent |
Select this check box if you want to restart the PATROL Agent after the policy is applied.
While editing a policy, if you select Restart Agent and provide the same default account information as what was provided while creating the policy, the PATROL Agent is not restarted. To restart the PATROL Agent, use the Query Agent screen. For more information, see Performing actions on a PATROL Agent
|
|
Tag |
Tags that you want to assign to the PATROL Agent. The format of each tag is tagName:tagDescription. If the tag description contains spaces, enclose the description within double quotes. You can also provide multiple tags, separated by commas. For example, tag1:"Brief Description",tag2:"Description". |
Integration Service |
An Integration Service or an Integration Service cluster that you want to set as the PATROL Agent phone home. The supported values are as follows:
- Single Integration Service
- Integration Service Cluster
|
Event Configuration Properties |
Event Forwarding Destination |
Destination where the events that are generated by the PATROL Agents must be sent to. The supported destinations are as follows:
- Integration Service Settings: Enables you to use the settings on the Integration Service to which the PATROL Agent is connected
- Cells: Enables to send the events to one or more cells. In the Event Cell List box, specify the cells to which you want to send the events, separated by commas. The format of each cell is cellName/cellPort, where cellName is the name of the cell and the cellPort is the port number through which the agent communicates with the cell. For example, cell1/1111,cell2/1203
Also, in the Event Cell Shared Key box, specify the shared key which is used for encryption. The default shared key is mc.
- Do not send events: Stops sending the events
|
Event Format Container |
String to append to the name of the events that are generated by the PATROL Agents. The default string is BiiP3. |
Back to top
Specify actions to be performed on the Infrastructure Management server when the policy is applied. The actions apply to all devices that are associated with the PATROL Agent and all the monitor instances that the Agent monitors.
- Click the Server tab.
- Specify values for the following properties:
Property |
Description |
Add Agent Monitors to Group |
Name of a group on the Infrastructure Management server under which you want to add the monitors that are created as a result of this policy.
You can provide multiple group names, separated by commas. If a group does not exist, a new group is created. Use a forward slash (/) to specify a group in a hierarchy. For example, server/device1/myGroup.
If more than one group exists with the same name and a distinct hierarchy is not specified, monitor instances are not added to the group. The group names are case sensitive. |
Add Associated Devices to Group |
Select the check box to add all devices associated with the Agent monitors to the group specified in the Add Agent Monitors to Group field. If multiple groups are specified in the Add Agent Monitors to Group field, all the associated devices are added automatically to all the groups.
|
Copy Baseline from Device |
Display name of the device from which you want to copy the baseline.
Baseline for the monitor instances that are created on the child servers as a result of the policy are copied from the baseline of the corresponding monitor instances on the specified device. Baseline can be copied from the specified device only if the device is available on the child server.
The device names are case sensitive. |
Associate Authorization Profiles with Devices |
Name of the user group on the child servers to associate with the devices that are created as a result of the policy.
Devices are associated with the specified user group only if the user groups are available on the child server. The user groups are given both read and write permissions to the Authorization Profile. You can provide multiple group names, separated by commas. The user group names are case sensitive. |
Back to top
Define and manage configuration variables
You can define individual configuration variables or import them from a ruleset file (.cfg).
The PATROL Agent configuration is saved in a set of configuration variables that are stored in the Agent's configuration database. You can control the PATROL Agent configuration by changing the values of these configuration variables. Also, you can define a configuration variable, and the definitions are set on PATROL Agent when the policy is applied.
To import existing configuration variables
- In the Configuration Variable page, click the common action menu in the table and select Import.
- Browse for and select the configuration file (.cfg) to be imported.
- Click Open. The variables from the file are added to the table.
To add new configuration variables
- Click Add Configuration Variable.
In the Add Configuration Variable dialog box, specify values for the following properties and click OK:
Property |
Description |
Variable |
Name for the configuration variable. Important: The variable names are case sensitive and must start with slash (/). You must enter the complete path for the variable, not just the name. If the intermediate variables do not exist, the variables are created. |
Operation |
Operation that you want to perform on the configuration variable. The supported operations are as follows:
REPLACE: Replaces the current value of the variable on the PATROL Agent if the variable already exists. Otherwise, a new variable is created with the specified value.
DELVAR: Deletes the variable from the PATROL Agent.
DELETE: Deletes the value of the variable, and the variable remains empty.
|
Value |
Value that you want to configure for the variable and click OK. The configuration variable is added as a new row in the Configuration Variables table. |
To add another configuration variable, repeat the earlier steps.
Important: For the defaultAccount
configuration variable, specify the value in the userName/password format. Note that the password can be a plain text or a PATROL Agent-encrypted string.
Examples:
patrol/patAdm1n
patrol/FA4E70ECEAE09E75A744B52D2593C19F
For the SecureStore
configuration variable, specify the value in the context/data format. Note that the context and data can be a plain text or a PATROL Agent-encrypted string.
Examples:
MY_KM1;MY_KM2;MY_KM3/mysecretdata
“EDC10278901F8CB04CF927C82828595B62D25EC355D0AF38589CE4
235A246F8C63F24575073E4ECD”
where “EDC10278901F8CB04CF927C82828595B62D25EC355D0AF38589CE4235A246F8C63F24575073E4ECD”
is the encrypted form of "MY_KM1;MY_KM2;MY_KM3/mysecretdata"
- To modify any value in a variable, click the action menu for the variable and select Edit.
In the Edit Configuration Variable dialog box, modify the properties and click OK.
- To remove a variable, click the action menu for the variable and select Delete.
Back to top
Comments
Log in or register to comment.