Every alarm action type allows you to select up to five severities. The alarm action will only trigger when used in a notification policy that is tied to an alarm threshold with a matching severity.
In the following example, User1 will only receive an sms message if a critical severity threshold is violated.
- An alarm action named "send_user1_sms” is created, and defined to send User1 an SMS e-mail for critical events only.
- The “send_user1_sms” action is added to a notification policy called “sms messaging.”
- The "sms messaging" notification policy includes various thresholds and device alarms. The alarms are of varying severity - some are set for critical, and some are set for warning. If an alarm occurs, User1 will only receive an SMS message for those thresholds and device alarms defined as critical.
You must select at least one severity.
|Information||Typically used to set up an alarm action to respond to events considered to be unimportant, but important enough to require alert notifications when they occur.|
|Warning||Typically used by SNMP devices to indicate a condition exists that may require attention to make sure it does not deteriorate into a critical state. For example, a UPS that is running on battery power during a power failure will shut down its load equipment if its battery power is depleted before power returns to normal.|
|Error||Typically used to indicate a sensor threshold violation requires immediate attention. For example, a high temperature violation that could lead to equipment damage.|
|Critical||Typically used by SNMP devices to indicate an operational failure requires immediate attention. For example, a battery that needs to be replaced can result in the loss of data at the UPS load equipment if a power failure occurs.|
|Failure||Typically used to indicate an operational failure requires immediate attention. For example, communication with a camera pod was lost which could lead to an undetected security violation.|