When you are creating or editing a monitoring policy, you can create thresholds for the monitor instances on the Infrastructure Management Server. For information about the types of thresholds, see How baselines, thresholds and Key Performance Indicators work together to generate events in the operator console.
Ensure that monitor configuration is complete before the thresholds are applied. Thresholds cannot be applied to monitors that are not configured through Central Monitoring Administration.
If you have not done so already, perform the steps provided under the following sections:
In the Instance Name box, type the name of the instance or a regular expression that can match multiple instances.
You can also specify an instance specific to a device. To specify an instance specific to a device, select Match Device Name, and in the Instance Name box, type the name of the instance with the associated device in the following format:
deviceName/instanceName
In the Attribute list, select a monitor attribute.
Note
In the Attribute list, some 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.In the Type of Threshold list, select the threshold type that you want to configure for the selected attribute. The supported types are as follows:
After you save or update a policy, the new threshold configurations are pushed to the selected BMC PATROL Agents.
After you update a policy, the updated threshold configurations are pushed to the selected BMC PATROL Agents.
After you delete a threshold configuration and save the policy, the deleted threshold configurations are removed from the selected BMC PATROL Agents.
Configuring a BMC PATROL Agent
2 Comments
Hal Devore
The "mechanics" of adding a server threshold are straightforward. However the "semantics" are not.
There is no mention that a regex can be used for the Instance Name (it can)
There needs to be discussion of "collisions" when two threshold settings using different instance patterns match the same threshold instance.
It's not at all clear how Agent Selection is used with Server Thresholds. Are Agents queried for matching instances? Is the process dynamic so that new instances and newly connected Agents automatically get the selected threshold?
Many questions, few answers...
Hal Devore
It is also unclear what happens if:
--Hal