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.
Name for the policy. The policy names must be unique. In an environment with tenants, the policy names must be unique for a single tenant. It is a mandatory field.
For more information, see Policy naming guidelines.
|Description||(Optional) A brief description about the policy|
|Associated User Group|
Name of the user group that is associated with the PATROL Agents as defined in the Authorization Profile or in the PATROL Agent ACLs. The policy is applicable to these PATROL Agents.
Note: The list of user groups that is displayed includes the user groups that the logged on user belongs to. For monitoring and blackout policies, this property determines the monitoring solutions and configuration options that you have. For more information about granting or restricting access, see .
This property can be viewed in READ-ONLY mode by other users of the user group. Only the owner of the policy can modify this property.
|Share with User Group|
Specify whether this policy is to be shared with the users across the associated user group or not. This property can be viewed in READ-ONLY mode by other users of the associated user group. Only the owner of the policy can modify this property.
Priority of the policy. Based on the precedence number that you configure, the configuration is applied to the PATROL Agents and the Infrastructure Management servers.
The precedence number ranges from 0 to 999. A lower number indicates a higher precedence. The default value is 900.
The configuration from a policy with a higher precedence overrides the configuration from a policy with a lower precedence. If two policies have the same precedence number, then the configuration from the latest created policy takes priority.
|Enable Policy||Indicates whether the policy is enabled or disabled. By default, the policy is enabled. If you disable a policy when you create it, the policy configurations are not applied to the PATROL Agents and the Infrastructure Management Servers. If you disable any existing policy, the policy configurations are removed from the PATROL Agents and the Infrastructure Management servers, where the policy was applied.|
Basic monitoring for Microsoft Windows operating systems that apply to all Microsoft Windows servers
Basic monitoring for Red Hat operating systems that apply to all Red Hat Enterprise Linux servers
Monitoring for Oracle databases that apply to all Oracle databases
Monitoring for SQL Server databases that apply to all SQL Server databases
Monitoring for Apache that apply to all Apache instances
Monitoring for WebLogic that apply to all WebLogic instances
Windows DSN Server monitoring
Windows DHCP Server monitoring
Select PATROL Agents.
Define conditions to select the PATROL Agents on which you want to apply the policy.
|Agent Host Name|
Host name of the computer on which the PATROL Agent is installed.
Note: The value for the matches property must be a strict regular expression. Some examples of regular expressions that can be used:
Port number through which the PATROL Agent listens for incoming connections from the PATROL console.
Use port numbers from 1025 to 65535.
|Agent Version||Version of the PATROL Agent.|
|Agent Operating System||Operating system of the computer on which the PATROL Agent is installed.|
|Agent IP Address||IP address of the computer on which the PATROL Agent is installed. If you select the Agent IP Address in the range condition, only IPv4 range is supported.|
|Agent Tag||Tag applied on the PATROL Agent.|
|Integration Service||PATROL Agents connected to the selected Integration Service.|
|Infrastructure Management Server||PATROL Agents connected to the selected Infrastructure Management Server.|
|Monitoring Solution Name1||PATROL Agents on which the selected monitoring solution is installed.|
|Monitoring Solution Version1||PATROL Agents on which monitoring solutions of the specified version are installed.|
|Tenant Name||Name of the tenant to which the PATROL Agent are associated via the Integration Service.|
is only applicable to PATROL Agent version 10.0 and later. 1 - The Monitoring Solution Name property
Note: The values that you enter for the properties are not case-sensitive.
You can set multiple conditions and also group the conditions to identify the agents.
Steps to select Agents:
To view the list of PATROL Agents that are selected based on the specified criteria, click Preview.
The Preview button is enabled only after you specify values for the selected conditions.
c. Specify values in at least one of the configuration tabs and click Save.
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:
|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 actions 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 List of Monitoring Solutions and KMs in Operations Management. To configure custom monitoring solutions, ensure the solution is structured correctly; for details, see .
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:
|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.
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.
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.
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.
The instance SID is not the monitoring instance name that is displayed in the Truesight console.
1. Log on to BMC TrueSight Infrastructure Management Operator console.
2. In the navigation pane, select Devices > Grid View.
3. Click any device.
4. The Show Monitors page is displayed.
5. Hover the mouse over the specific monitor instance, and the tool tip displays the SID for the instance.
6. Note down the SID. You can use the SID value when you configure the agent threshold.
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.
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
- Monitor Type
- 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.
Click Add Agent Threshold.
Specify values for the following properties:
|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.|
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:
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.
To configure the server thresholds:
Specify values for the following properties:
|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:
Click here to view the supported characters for regular expressions
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 .
Click the Agent tab.
Specify the following properties:
|Agent Default Account|
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|
Select this check box if you want to restart the PATROL Agent after the policy is applied.
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.
|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.
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.
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.
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:
|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:
defaultAccountconfiguration variable, specify the value in the userName/password format. Note that the password can be a plain text or a PATROL Agent-encrypted string.
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.
“EDC10278901F8CB04CF927C82828595B62D25EC355D0AF38589CE4235A246F8C63F24575073E4ECD” is the encrypted form of "MY_KM1;MY_KM2;MY_KM3/mysecretdata"