Configure Count-Based Threshold Monitoring for Node Groups

Count-Based Threshold Settings enable you to determine as soon as a threshold is reached (for example, the CPU utilization for a node reaches 90%).

To establish count-based threshold monitoring behavior for nodes:

  1. Prerequisite. Before setting thresholds, analyze performance data over time to determine wise threshold settings for each Node Group. For more information, see the following topics:

  2. In the Node Settings form, navigate to the Threshold Settings tab.
  3. Do one of the following:

    • To create a threshold definition, click the New icon and select Count-Based Threshold Settings.
    • To edit a threshold definition, select a row and click the Open icon.
    • To delete a threshold definition, select a row and click the  Delete icon.
  4. Select the Monitored Attribute you want to monitor and establish the threshold values for that attribute (see Basic Count-Based Threshold Settings table).

    When you configure thresholds using this technique, NNMi uses the assigned Node Group as a filter (only monitoring the threshold for nodes belonging to the specified Node Group).

  5. Click  Save and Close to return to the Node Settings form.
  6. Click  Save and Close to return to the Monitoring Configuration form.
  7. Click  Save and Close. NNMi applies your changes during the next regularly scheduled monitoring cycle.

    Note Threshold Incidents are disabled by default within NNMi to prevent Incident storms. If you are ready to generate Threshold Incidents, see Generate Performance Threshold Incidents (NNM iSPI Performance for Metrics). See also Custom Incident Attributes Provided by NNMi (Information for Administrators) for a description of the special custom incident attributes available in Threshold Incidents.

  8. See also Find Threshold Results.

Basic Count-Based Threshold Settings
Attribute Description
Monitored Attribute

In the Monitored Attribute drop-down list, select the attribute for which you want to establish a threshold configuration.

Tip Some of the choices in the Monitored Attribute selection list do not apply in this context.

See the tables in About Threshold Settings Provided by NNMi for information about which Monitored Attributes are available for Node Groups.

A High Threshold situation occurs when:

The Monitored Attribute is greater than the High Value for High Trigger Count cycles.

When these criteria are met, NNMi does the following:

  • Updates the Threshold's state value to  High for the appropriate Interface.
  • Generates the related incident (if one is Enabled ). If an incident is generated, NNMi closes that incident when the Threshold criteria are no longer met.
High Value

The value that above which becomes a threshold situation. Use one of the following:

  • Designate a percentage between 0.00 and 100.00.

    For special situations, the following values can be used:

    • 0.000000000000001 (or 1E-15 in Scientific Notation) for the smallest value greater than zero.
    • 99.99999999999999 for the highest value less than one hundred.
  • Designate any appropriate integer value (for example, a Management Address ICMP Response Time of 0 or greater milliseconds ).

The High Value must be greater than or equal to the designated Low Value.

If you use the highest possible value, the threshold is disabled because it cannot be crossed.

High Value Rearm

The High Value Rearm designates the lower boundary of the High Threshold range of values.

After entering a High threshold situation, when a returned value is below the specified High Value Rearm, the High Threshold situation ends (for Count-Based Thresholds).

Note The High Value Rearm must be less than or equal to the High Value and greater than or equal to the Low Value Rearm.

High Trigger Count

Designate the number of consecutive polling intervals the returned value must be greater than the specified High Value to meet the High Threshold criteria. The default value is 1.

Tip If the polled value represents an average over the configured polling interval, a trigger count of 1 is often appropriate.

See the currently configured Fault Polling Interval or Performance Polling Interval setting that is influencing the Monitored Attribute you chose, because that is how often NNMi provides a data point. See the tables in About Threshold Settings Provided by NNMi for details. See the following topics for instructions about finding the current polling interval setting:

A Low Threshold situation occurs when:

The Monitored Attribute is less than the Low Value for Low Trigger Count cycles.

When these criteria are met, NNMi does the following:

  • Updates the Threshold's state value to  Low for the appropriate Interface.
  • Generates the related incident (if one is Enabled ). If an incident is generated, NNMi closes that incident when the Threshold criteria are no longer met.

Low Value

The value that below which becomes a threshold situation. Use one of the following:

  • Designate a percentage between 0.00 and 100.00.

    For special situations, the following values can be used:

    • 0.000000000000001 (or 1E-15 in Scientific Notation) for the smallest value greater than zero.
    • 99.99999999999999 for the highest value less than one hundred.
  • Designate any appropriate integer value (for example, a Management Address ICMP Response Time of 0 or greater milliseconds ).

The Low Value must be less than or equal to the designated High Value.

If you use the minimum possible value, the Low threshold is disabled because it cannot be crossed.

Low Value Rearm

The Low Value Rearm designates the upper boundary of the Low Threshold range of values.

After entering a Low threshold situation, when a returned value is above the specified Low Value Rearm, the Low Threshold situation ends (for Count-Based Thresholds).

Note The Low Value Rearm must be greater than or equal to the Low Value and less than or equal to the High Value Rearm.

Low Trigger Count

Designate the number of consecutive polling interval the returned value must be less than the specified Low Value to meet the Low Threshold criteria. The default value is 1.

Tip If the polled value represents an average over the configured polling interval, a trigger count of 1 is often appropriate.

See the currently configured Fault Polling Interval or Performance Polling Interval setting that is influencing the Monitored Attribute you chose, because that is how often NNMi provides a data point. See the tables in About Threshold Settings Provided by NNMi for details. See the following topics for instructions about finding the current polling interval setting: