Alert
Review, check, and resolve fired alerts, and manage which channel and recipients each alert is delivered to (delivery rules).
Launching the Alert app from the desktop shows two screens under the Alerts group in the left sidebar.
| Screen | Description |
|---|---|
| Alert board | List of fired alerts (Alert status board). Review by state, severity, and target, and process them with Acknowledge / Resolve |
| Delivery settings | Manage alert delivery rules — define which alerts are sent, to which channel, and to whom |
Access scope
Reviewing/acting on alerts and viewing/creating delivery rules are controlled by IAM permissions. The visible scope (system-wide / domain / granted scope) depends on your role.
Alert Lifecycle
An alert goes through three states from firing to close.
Firing → Acknowledged → Resolved- Firing — the condition is met and the alert has fired
- Acknowledged — an operator has marked it as seen (repeat notifications stop immediately)
- Resolved — handling is complete and the alert is closed (a Comment is recorded)
State Transition Rules
- Manual: the order
Firing → Acknowledged → Resolvedis enforced (you cannot Resolve without acknowledging first). - Automatic (Auto Resolve): when the condition clears, the system closes the alert directly from Firing or Acknowledged to Resolved.
- Resolved alerts remain viewable in the UI for 90 days.
Severity
| Severity | Meaning |
|---|---|
| Critical | A failure that needs immediate action (e.g., OSD Down, disk almost full) |
| Warning | A state that needs attention (e.g., high node disk/memory usage) |
Delivery Channels
Delivery settings let you assign a delivery channel per alert.
- Notification Center — the default channel (always on). Delivers to the selected Users and User groups
- Email — sends to recipient email addresses
- Slack — sends to a Slack channel Webhook URL