Alarm severity levels in OpManager
OpManager has four different severity levels for the alarms. Severity levels of device down alarms (availability monitoring) are already predefined.
Here is the list with the severity and the events which will trigger the alarms with these severity :
1)Service Down: When is service down and URL monitor is down
2)Attention: When the device is down for the 1st poll in availability
3)Trouble: When the device is down for 3 consecutive polls in Availability
4)Critical: When the device is down for 5 consecutive polls in Availability. This is the highest severity in OpManager.
5)Clear: At any stage if an alarm is cleared.
As you can see, the severity will automatically change for the device down alarms based on the number of missed polls.
Similar to device down alarms, Interface down alarm severity(Trouble) is also predefined.
But for other alarms like threshold violation, Traps and event logs, user can configure any severity(Attention or Trouble or Critical) and the severity will be the same even if the alarm is repeated.
Here is the list with the severity and the events which will trigger the alarms with these severity :
1)Service Down: When is service down and URL monitor is down
2)Attention: When the device is down for the 1st poll in availability
3)Trouble: When the device is down for 3 consecutive polls in Availability
4)Critical: When the device is down for 5 consecutive polls in Availability. This is the highest severity in OpManager.
5)Clear: At any stage if an alarm is cleared.
Similar to device down alarms, Interface down alarm severity(Trouble) is also predefined.
But for other alarms like threshold violation, Traps and event logs, user can configure any severity(Attention or Trouble or Critical) and the severity will be the same even if the alarm is repeated.
New to ADSelfService Plus?
Related Articles
Escalating alarms in OpManager
Configuring Alarm suppression for devices in bulk or one at a time in OpManager
Daylight Saving Time(DST) not being updated in the OpManager
Issue: Daylight Saving Time(DST) difference is not reflected in OpManager. The Time that is being shown in "About" tab in OpManager UI will have 1 hour time difference with respect to the actual time. Reason: Daylight Saving Time(DST) changes that ...REMOVING UNSOLICITED TRAPS FROM OPMANAGER DATABASE
Connect to OpManager database and execute the below query : Refer the link below to connect to OpManager database : https://support.zoho.com/portal/manageengine/helpcenter/articles/connecting-to-the-opmanager-database 1. Run this command from the ...ADDING 3rd PARTY UPS in OpManager
Any type of UPS can be monitored by making some configuration changes, provided the corresponding mib supports all the monitored parameters. Here are the details of the configuration changes. (Example: Powerware UPS - Powerware mib supports most of ...