The following is an example of the alarm lifecycle based on a
nodeLostService event is received and creates a new alarm.
Clicking the number displayed in the Count column displays the corresponding events and their details.
The alarm clears automatically when service is restored, based on a
If the problem occurs again, the events are reduced into the existing alarm. The alarm’s count is updated to reflect the new activity.
The alarm once again clears immediately when service is restored.
Note that the alarm’s count only increments on events with a severity of Warning or greater.
Alarms are deleted from the Meridian database after a set amount of time.
This lifetime can be configured via Drools rules in the
The default alarm lifetimes:
Cleared and Unacknowledged
Cleared and Acknowledged
Active and Unacknowledged
All other alarms
These delays are based on the last event time, and will restart the counter if a new problem event is reduced into the same alarm.