Managing alarm history
Every asset has its own alarm history generated by its template's rules — see the detail in Asset alarm history.
This page covers cross-cutting concepts for managing alarms across your Space.
Alarm states
- Active: the condition is still met.
- Acknowledged: someone on the team has taken ownership of the event.
- Resolved: the condition is no longer met.
Goals for this page
- Explain whether/how an aggregated view of active alarms across all assets exists (cross-asset), in addition to the per-asset view.
- Explain any push/email notifications generated when an alarm's status changes.
- Explain permissions: who can acknowledge an alarm (likely Admin and Support).