NDU provides the ability to create and manage alarms related to your entities: devices, assets, customers, etc.
Alarms have a lifecycle. Each Alarm can be cleared and acknowledged. By default, an alarm is not in the active and unacknowledged state.
Alarm Originator is an entity that is responsible for triggering an alarm. By default, an alarm is propagated to all related entities (parent relations only). An alarm is identified by start time, originator and type. There can’t be two active alarms for a same type and originator.
One of the following alarm severities is supported: CRITICAL, MAJOR, MINOR, WARNING, INDETERMINATE.
Alarm entity may be updated by external applications or NDU rules. Alarm keeps track of both clear and acknowledge time and latest change as an end time.
NDU provides REST API to manage and query alarms.
It is possible to create, update and clear alarm using NDU rule engine <!– Please find more details about Alarm Rule Nodes:
Also, in this step-by-step guide you can see how to create/update/clear Alarms in real-life scenarios: