When an alert is raised, a special Alert event is generated and persistently stored in AggreGate Server database. Alert events that are not acknowledged are called pending alert instances. See the events topic for more information about events and event acknowledgement.
|
It's important to distinguish Active and Pending alert instances. |
Managing Pending Alerts
The pending instances of every alert may be controlled using the Manage Pending Instances action, defined in the Alert context. This action shows when and why the alert was raised, and lets you delete or acknowledge pending alerts. Alert instances that have already been acknowledged are not shown in the list.
Here is what the list of pending alerts looks like (screenshot made in AggreGate Client):
When one or more unacknowledged alert events exist, the alert remains in Active state. This state is indicated in AggreGate Server User Interfaces by a special 
icon. The active state indicates that some attention is required to solve the problem indicated by an alert. When the problem is solved, system operator may launch the View Pending Alerts action and acknowledge all pending alert instances. Alert will be put back in the "Enabled" (normal) state, indicated by the 
icon.
Non-acknowledged instances may force alert to switch into the Active state only if the Allow pending alerts setting is enabled.
Viewing Pending Instances
To see pending instances of a certain alert, launch View Status action and check Active Instances table. Pending instances have Pending mark in the Type column.
To see all pending alerts in the system, run Active Alerts query.
Disabling Pending Alerts
When configuring an alert, one of the properties is called Allow Pending Alerts. If you disable this (i.e, disallow pending alerts for this particular alert you're configuring), the alert won't be shown in the Pending Alerts list even if it wasn't acknowledged. It also won't be escalated.