When alert is raised, a special AggreGate Server event is generated in the Alert context. It is called "Alert event" or "Alert instance", and has several uses:
| • | When this event is not acknowledged, it is called "pending alert instance". When an alert has pending instances, the alert itself is put into the Active state. Its icon changes to  . This is similar to how an email client works -- you can see your mailbox as "Unread" if it has unread messages in it. |
| • | History of the Alert Event helps to keep track when and why the alert was raised. |
When you View Pending Alerts, you are actually looking at the history of all Alert Events for a particular alert. You can only access this action if the Allow Pending Alerts setting is enabled for this alert.
Format of Alert Event:
Field |
Description |
Alert Name |
Name of alert context. |
Alert Description |
Description of alert context. |
Context |
Path of context for which the alert was raised, i.e. context where event or state change monitored by alert trigger has occurred. |
Entity |
Event (is raised by event trigger) or variable (if raised by variable trigger) which caused the alert. |
Cause |
Textual description of alert's cause. |
Message |
Alert message. This is a manually configured string, which is supposed to be a human-readable description of the alert (i.e, "The house is on fire"). See Alert Configuration section. |
Trigger |
Trigger message. Additional text message provided by alert trigger. |
Alert Data |
Data associated with the event causing the alert. This field is NULL (not defined) if the alert was caused by a certain variable state or by a variable value change. For a login event defined in the Users context, this data table will contain one record with two fields: Username and Permissions. |
Example of Alert event:
