Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
Search for | Example | Results |
---|---|---|
A single word | cat
|
Topics that contain the word "cat". You will also find its grammatical variations, such as "cats". |
A phrase. You can specify that the search results contain a specific phrase. |
"cat food" (quotation marks) |
Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase. |
Search for | Operator | Example |
---|---|---|
Two or more words in the same topic |
|
|
Either word in a topic |
|
|
Topics that do not contain a specific word or phrase |
|
|
Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
A combination of search types | ( ) parentheses |
|
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:
-
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:
-
Navigate to the Node Settings form.
- From the workspace navigation panel, select the Configuration workspace.
- Expand the Monitoring folder.
- Select Monitoring Configuration.
- Navigate to the Node Settings tab.
-
Do one of the following:
- To create an Node Settings definition, click the New icon.
- To edit an Node Settings definition, select a row and click the Open icon.
- In the Node Settings form, navigate to the Threshold Settings tab.
-
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.
-
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).
- Click Save and Close to return to the Node Settings form.
- Click Save and Close to return to the Monitoring Configuration form.
-
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.
-
See also Find Threshold Results.
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:
|
|
High Value |
The value that above which becomes a threshold situation. Use one of the following:
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:
|
|
Low Value |
The value that below which becomes a threshold situation. Use one of the following:
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: |
We welcome your comments!
To open the configured email client on this computer, open an email window.
Otherwise, copy the information below to a web mail client, and send this email to network-management-doc-feedback@hpe.com.
Help Topic ID:
Product:
Topic Title:
Feedback: