Managing alarm history
Each asset has its own history of alarms raised by its template rules — see Asset alarm history.
This page covers concepts that apply across the whole Space.
Alarm statuses
| Status | Meaning |
|---|---|
| Active | The condition is still true |
| Acknowledged | Someone on the team has taken ownership |
| Resolved | The condition is no longer true |
Where to manage them
- Per asset: Alarms tab on the detail page (filters, acknowledge, jump to Trend).
- From the asset header: quick chip/dialog for active alarms.
- There is no dedicated cross-asset view: for a Space-wide overview use the AI assistant (e.g. "which alarms are active?") or filter the asset list.
Notifications on state change
Email notifications (if configured on the rule) fire when all rule conditions stay true for the configured delay. Each notification row has its own send count and resend delay. Acknowledging in the UI does not by itself send a new email.
Permissions
Admins and Support can acknowledge alarms. Customers see history for assets they can access.