Child pages
    • Configuring a server threshold
    Skip to end of metadata
    Go to start of metadata

    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.

    Before you begin

    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:

    To add and configure monitor thresholds on the server

    1. On the Server Threshold Configuration page, click Add
    2. In the Add Instance Thresholds dialog box, select a solution, its version, and a monitor type.
    3. 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


    4. 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.

    5. 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:

      • Absolute
      • Signature
      • Abnormality
    6. Configure the threshold parameters. The parameters vary based on the threshold type that you have selected.
    7. Click Add to add the configuration details for the threshold.
    8. (Optional) To configure more thresholds, repeat step 2 through step 7.
    9. (Optional) To reset the settings to the default values, click Reset.
    10. When you finish configuration, click Close.
    11. Click Next or Finish.

    After you save or update a policy, the new threshold configurations are pushed to the selected BMC PATROL Agents.

    To edit a threshold configuration

    1. On the Server Threshold Configuration page, select a threshold definition, and click Edit .
    2. Update the configuration values, and click Update.
    3. After updating the threshold configuration, click Close.

    After you update a policy, the updated threshold configurations are pushed to the selected BMC PATROL Agents.

    To delete a threshold configuration

    1. On the Server Threshold Configuration page, in the Defined attribute thresholds table, perform one of the following tasks.
      • To delete all the threshold configuration based on a solution name and all its version, in the Solution column, select a value. 
      • To delete all the threshold configuration based on a version of the monitoring solution and its monitor types, in the Version column, select a value.
      • To delete all the threshold configuration based on a monitor type and its attributes, in the Monitor Type column, select a value.
      • To delete all the threshold configuration based on the scope, in the Scope column, select a value.
    2. Click Delete .
    3. In the Delete Confirmation dialog box, click Yes.

    After you delete a threshold configuration and save the policy, the deleted threshold configurations are removed from the selected BMC PATROL Agents.

    Where to go from here

    Configuring a BMC PATROL Agent  

    Specifying server configuration 

    Defining a configuration variable

    2 Comments

    1. 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...

    2. It is also unclear what happens if:

      • CMA Server Threshold policies are in effect and someone edits an Instance threshold using the older threshold edit pages in the operational console
      • CMA Global Thresholds are set and someone edits a global threshold in the older threshold edit pages in the operational console
      • CMA Server Threshold policies or CMA Global Thresholds are in effect and someone edits a threshold via the Edit Violated ... Threshold menu pick on a threshold violation event

      --Hal