Alert Escalation

Pending alerts may be escalated. Escalation is usually used to draw attention to some critical conditions. In most cases, escalated alerts, indicated with the icon, require the system operators to take quick action.

For an alert to be escalated, there has to be at least one pending (unacknowledged) instance of it, and it must satisfy at least one of the escalation rules defined by the Alert Escalation property. There are two escalation types:

With number-based escalation, an alert is escalated if the number of pending alert instances exceeds the limit specified by the Number of pending alerts required to initiate escalation setting.

With time-based escalation, an alert is escalated if any pending instance (alert event) is not acknowledged within the time frame specified by its Time before escalation setting.

When an alert is escalated, an Escalation Notification is emailed to all recipients defined by the Notifications setting. This notification contains the time of escalation, and the reason for it:

The reason is also shown in a tooltip that appears when the mouse hovers over the alert in AggreGate Server User Interfaces. Here is what it looks like in AggreGate Client:

To put an alert back in pending or normal state, acknowledge some of its pending instances so that escalation rules will not be satisfied.