Viewing assistance
To toggle full-screen mode for this topic (recommended), type f. To hide the navigation tree on the left, type [.
In the Create Monitoring Policy page, specify the monitoring policy properties:
Define the general properties.
Select PATROL Agents.
c. Specify values in at least one of the configuration tabs and click Save.
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 List of Monitoring Solutions and KMs in Operations Management. 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 Monitoring 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:
To know the list of monitor types that are loaded on the Agent, click the Information icon . Tip: For documentation or more information about a monitor profile or monitor type, click the Help icon next to the list. The online documentation for that monitor type is displayed. |
Other configuration options | Specify values for additional configuration options. These options vary depending on the monitoring solution, monitor profile, and monitor type that you selected. Tip: For information about an option, move the mouse over the option to view the tooltip. |
The following figure shows the Add Monitoring Configuration dialog box with sample data. Also, you can see the tooltip that provides helpful information about the Exclude Criteria option.
After you save or update a policy, the monitor type configurations are pushed to the selected PATROL Agents
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 restrict or allow data and events to be sent to the Infrastructure Management server. Unlike in blackout policies, when you apply filters in a monitoring policy, the data collection and event generation continues on the PATROL Agent.
You can configure the following types of filters:
Instance-level filter - When you apply this filter, information about both attributes and instances is not sent to the TrueSight Infrastructure Management server. If you have instances in a parent-child hierarchy, you must configure instance-level filters separately for each sub-node of the parent and child.
Note
The instance-level filter is available for the PATROL Agent version 10.7 or later. The instance filtering policies are ignored on any earlier version of the PATROL Agent.
A PATROL Agent applies a filtering policy during the next scheduled discovery or collection of a PATROL object (monitor type or attribute). That is, filtering is applied when the first collection occurs on the PATROL object after filtering rules are applied. Due to this behavior, there might be a delay in the deployment of the filtering rules on the PATROL object.
Best Practice
Complete the following steps to configure filters:
If you want to specifically filter data and events from an instance on the PATROL agent, select Instance, and then enter the instance name in the Instance SID field.
Tip
The instance SID is not the monitoring instance name that is displayed in the Truesight console.
For the Instance SID field, you can also use a regular expression.
If you want to use a regular expression, select the Is a Regular Expression check box.
Note
The value for the matches property must be a strict regular expression. Some examples of regular expressions that can be used:
Select a filtering option according to the following table:
Options for filtering attributes | Options for filtering instances |
---|---|
|
|
Click any of the following:
Specify the time interval between two consecutive data polls. You need to specify a separate poll interval for every parameter.
Select values for the following options:
- Monitoring Solution - Version - Monitor Type - Parameter - Parameter Polling Interval |
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.
Best Practice
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 |
Scope | Scope of the threshold. Select one of the following options:
|
Monitor Attribute | Monitoring attribute |
Threshold Ranges: Configure border and threshold ranges for the selected monitor attribute. |
|
For Border Threshold, 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.
Note
|
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:
|
You can create thresholds for the monitor instances on the Infrastructure Management server. For information about the types of thresholds, see Server thresholds, KPIs, and baselines.
Best Practice
To configure the server thresholds:
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:
|
|||||||||||||||||||||||||||||||
Monitor Attribute |
Monitor attribute
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: Configure the threshold parameters for the threshold type that you have selected. You can select either of the following types: Absolute, Signature, and Abnormality. |
||||||||||||||||||||||||||||||||
|
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. Note: You need to provide an Agent user name and password only if they are different from what was previously configured. |
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. Note You must select this check box if you want the user name change to take effect.
|
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:
|
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:
|
Event Format Container | String to append to the name of the events that are generated by the PATROL Agents. The default string is BiiP3. |
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.
Best Practice
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. Note This field is applicable and is functional only when you have a TrueSight Infrastructure Manager Server 10.5 or later in your environment. The devices from TrueSight Infrastructure Manager Server 10.1 and 10.0 are not added to the group even if this flag is selected. |
Copy Baseline from Device | Display name of the device from which you want to copy the baseline. |
Associate Authorization Profiles with Devices |
Name of the authorization profile to associate with the devices that are created as a result of the policy. Authorization profiles provide role-based access control by associating users who belong to one or more user groups with specific roles and objects. The default authorization profiles are created during the installation of the TrueSight Presentation Server component. Devices are associated with the specified authorization profile only if the authorization profile is available on the Presentation Server. You can provide multiple authorization profile names, separated by commas. The authorization profile names are case sensitive. If you want to disassociate the devices from the authorization profiles after a policy is disabled or deleted, use the Authorization Profiles page in the TrueSight console and remove each device from the authorization profile.. |
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. Configuration variables that are defined on PATROL agents are retained even after disabling the policy. To delete the configuration variables, you must purge the PATROL Agent by using the following command:
pconfig +PURGE -p <port> -host <hostname>
By using this command, the configuration variable values of the PATROL Agent are restored to the default state, and the PATROL agent does not retain the previous configuration after an installation or an upgrade.
You can also remove the variables by using the Add Configuration Variable dialog box.
Note
To view the configuration variables that are available in the previous PATROL Agent versions, use the Query Agent functionality.
If you are modifying the default Agent configuration, you must restart the PATROL Agent to reflect the changes.
Best Practice
Note
The import operation supports only REPLACE, DELETE, and DELVAR operators. If the .cfg file contains the MERGE or APPEND operators, the file cannot be imported. You must delete these operators before importing the file.
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:
|
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. |
Click any of the following:
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"
8 Comments
Patrick Mischler
How do I disable a server threshold?
Use case: For the majority of the system a global server threshold is applied. But this threshold should not apply for a distinct group of servers. How can the global server threshold be disabled in a monitoring policy?
Harihara Subramanian
Hi Patrick Mischler,
Thanks for your comment.
Kartik Peyyeti, can you please respond to Patrick Mischler's use case?
Thanks,
Hari
Jeff Wenzbauer
This page states "Note: The values that you enter for the properties are not case-sensitive." in the section titled "To create a monitoring policy."
I find that this is not true. When creating a policy, in my 'Agent Selection Criteria' if I use 'Agent Host Name' matches .*test.*, this will not match an agent with a hostname of MYTEST but it will match an agent with a hostname of mytest. Is there a way to ignore case when using the 'matches' operator?
Harihara Subramanian
Hello Jeff Wenzbauer,
We are working on this comment to validate before updating the doc. Thanks for your observations.
Thanks,
Hari
Priyanka Nanwani
Hi Jeff,
Thank you for reporting this issue. The values that you enter for the properties are in fact case sensitive. The note is now corrected.
To ignore the case, you can use a regular expression with the matches operator.
For example, suppose, you want to select Agents with the following names:
In this scenario, you can provide the following agent selection criteria:
Agent Host Name matches [BMC,bmc].*
Hope this helps,
Priyanka
Jeff Wenzbauer
You can also use (?i) to indicate a case-insensitive search.
For example, (using your same example) suppose, you want to select Agents with the following names:
In this scenario, you can provide the following agent selection criteria:
Agent Host Name matches (?i)bmcagent
Harihara Subramanian
Priyanka Nanwani