An alert is a response of the system to a custom user-defined event or condition.
Alerts are raised by triggers (alert conditions). A trigger can be an event, a state or a change of state of a system component/hardware device. See the triggers section for details.
When an alert is raised, the system responds to it:
| • | The alert owner may be immediately notified, if he is connected to the server. He may also be prompted to acknowledge the alert. |
| • | E-mail messages may be sent to the alert owner, to a system user(s) or to a custom E-mail address(es). |
| • | The alert may be stored in the event history as a usual event. |
| • | The alert may change its state. |
|
Every user has their own set of alerts. |
Administering Alerts
Two contexts are used to administer alerts: One is the general Alerts context, which serves as a container. The other is the Alert context, which holds the information for one alert. |
|
Alerts are activated by triggers. Every alert may have several triggers associated with it. Each trigger defines a condition in which the alert should be raised. There are two types of triggers, described below:
|
Trigger: an act that sets in motion some course of events. |
Each alert may define zero or more triggers of every type. If no triggers are defined, the alert is never raised. If several triggers are defined, they act separately -- each trigger may raise the alert (they don't all have to exist at the same time -- just one is enough to raise the alert).
Alert Notifications
When an alert is raised by one of its triggers, AggreGate Server starts sending notifications and executing corrective actions.
Alert state indicate current severity of the alert. It involves several factors, such as availability of pending alert instances, trigger activity, and escalation rules.
See Alert States for details.
Built-In Alerts
Device Offline alert is built into AggreGate Server basic distribution package. It is raised when any Data Terminal is disconnected from the server for longer than 10 minutes.
According to its Variable Triggers, this alert is triggered only for Devices whose Enable Offline Alert setting is active.
Device Offline alert is owned by default administrator.
Failover alert is raised once the Master Node of AggreGate Server failover cluster fails and control is taken by a Failover node. An e-mail message is sent to the default administrator upon this alert.
Some examples of real-world alert configurations are provided in the Alert Examples section.