Configuring thresholds for performance monitors
Configuring thresholds enable OpManager to proactively monitor the resources and the services running on the servers and network devices, and raise alerts before they go down or reach the critical condition. OpManager offers multiple threshold levels namely:
- Attention threshold - low severity
- Trouble threshold - medium severity
- Critical threshold - high severity
- Rearm - to rearm the alert after it has been triggered
You can configure multiple thresholds for the monitors that are associated to a single device, and even configure them from a device template in order to apply across multiple devices. Also, if you are going to enable custom dials, the thresholds configured for the monitor will also be applicable for the custom dial, and the color of the dial will change in real time based on the status of that monitor.
Configure threshold limits for performance monitors in an individual device
- Go to the device snapshot page.
- Click Monitors → Performance Monitors → click on the edit icon corresponding to the monitor for which you want to configure threshold limits. Edit Monitor page opens.
- Ensure that the monitoring Interval is configured.
- Specify the unit for the monitored resource in terms of percentage, MB, KB etc (based on how the parameter is measured).
- Select the condition [>,=, <, or !=] for Warning Threshold, Trouble Threshold & Error Threshold, and enter the value. Alert is raised if the monitored value is greater than, equal to, not equal to, or lesser than (which ever is selected ) the threshold value.
Also, for = operator, you can provide multiple values using pipe '|' as the separator. Note that this is applicable only for thresholds configured from Device Snapshot → Monitors.
- Enter the Rearm Value. Rearm is the value that determines when the monitor is reverted back to 'Normal' status.
Example: The Warning threshold condition for a memory monitor is selected as greater than [>] and the threshold value is configured as 75. If the value of the monitor oscillates between 72, 80 and 73 for three successive polls, an alert is not raised for the poll with value '80' but the admin might still wish to receive an alert for it.
Note that if you set the thresholds' conditions using '>' criteria, then the rearm value can only be set using '<=' and vice versa.
To avoid this, you can set the Rearm value at a considerably wide interval (say 70 in this situation) to make sure the status returns to 'Normal' only when the value goes below this threshold.
- In the Consecutive Times field enter the value of how many consecutive times the thresholds (Attention, Trouble and Critical) can be violated to generate the alert.
- Click on Save.
Configure threshold limits for multiple devices of same type using Device Template
Configure from the Performance Monitors page:
- Go to Settings → Performance monitors and click the 'Edit' icon next to the monitor of your choice.
- Change the threshold values as required and click 'Save'.
- Once it's done, click the 'Associate' button next to the monitor to associate it to the necessary devices.
Configure from the Adaptive Thresholds page:
- Go to Settings → Monitoring → Monitor Settings.
- Select the "Adaptive Thresholds" tab, enable the checkbox and click 'Save'. You can also enable each monitor type individually at a global level by clicking on the little switch buttons next to each monitor and disabling the other monitor type(s).
Note: As of now, adaptive thresholds can only be configured for CPU utilization, Memory Utilization and Response Time monitors.