Alarm Escalation

Using this option, you can escalate if any alarm has not been attended to for a given time period. You can configure rules to send Escalation emails or send SMS or to Execute Program about unattended alarms to the Admin or to the superior.

To configure alarm escalation in Applications Manager, follow the steps given below:

1. Under the Settings tab, click on Alarm Escalation icon.
2. Click on New Rule link to add a new rule.
3. Configure the rule based on which alarm needs to be escalated by specifying the following details:
   • Specify the severity with which the alarm needs to be escalated. (Critical/Warning)
   • Select the resources for which the alarm needs to be escalated using any one of the following options:
     • All Monitors: Escalates the alarm for all the monitors in the server.
     • Monitor Groups: Escalates the alarm for selected Monitor Groups in the server.
     • Select Monitors: Escalates the alarm for selected monitors in the server.
     • Monitors in Monitor Groups: Escalates the alarm for the monitors that are present in the selected Monitor Groups.

4. Under Send EMail / SMS / Execute Program Actions, select the required action to be performed from the dropdown and then specify the time limit (in hours/minutes) beyond which the alarm needs to be escalated if it remains uncleared within that time period. You can configure multiple escalations levels as well as enable notification through multiple actions for a single Alarm Escalation rule, if required.

   Note:

   • Before configuring the required action from the dropdown, these actions have to be created first from the Actions tab located at the top band in order to be displayed in the dropdown. For more information on creating actions in Applications Manager, refer here.
   • By default, each Alarm Escalation rule supports upto five escalation levels, which can be modified by specifying the required limit for Maximum Alert Escalation Levels option located under Settings → Action/Alarm Settings.
5. Set the time period (in minutes) for how often the rule should be executed repeatedly.
6. By choosing not to receive duplicate escalation for the same alarm, you opt for optimizing the number of escalation EMails/ SMS sent and Program Action executions. For eg., If there are five critical alarms that were escalated in the first execution run (say 10 minutes), only if there is an addition of new alarm or deletion of alarm, the next set of alarms will be escalated in the second run. If there is no change in the environment in the next 10 minutes, ie., if the five critical alarms still remain the same, escalation EMail will not be sent.
7. Enable the Ignore Acknowledged Alarms to ignore the alarm escalation that is acknowledged/attended by the technician (which can be found under Alarms tab).
8. Click Save after specifying all the required rule criteria.

Note: Replaceable tags are not supported in Alarm Escalation Rule.