Alert Escalation
Pending alerts may be escalated. Escalation is usually used to draw attention to 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:
Number-based escalation
Time-based escalation
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:
Escalation reason: Alert was not acknowledged in 1 minute, threshold is 1.
Time: Mon Dec 10, 17:57:57 EST 2025The reason is also shown in a tooltip that appears when the mouse hovers over the alert in Iotellect Server User Interfaces.
To put an alert back in a pending or normal state, acknowledge some of its pending instances so that escalation rules will not be satisfied.
 | Alert escalation rules may not seem flexible enough. However, there's an easy way to escalate an alert in any custom case, send custom notifications upon this escalation, and execute custom corrective actions upon the escalation. Just set up a second alert whose triggers will:
This second "escalation" alert will have its own notification rules and corrective actions. |
Was this page helpful?