Alert States
Understand how alerts transition between open and resolved states in Sazabi.
Alerts in Sazabi have a simple lifecycle with two primary states. Understanding these states helps you manage alerts effectively and ensure nothing falls through the cracks.
Alert states
Open
When Chat creates an alert, it starts in the open state. Open alerts represent issues that actively need attention from your team.
Open alerts:
- Appear in your dashboard inbox
- Trigger notifications to configured delivery channels
- Are subject to deduplication if the same issue re-fires
- Remain visible until explicitly resolved
Resolved
When an issue has been addressed or is no longer occurring, you mark the alert as resolved. Resolved alerts move out of your active inbox but remain accessible in alert history.
Resolved alerts:
- No longer appear in the active inbox
- Do not trigger new notifications
- Can be searched in alert history
- Can re-open if the same issue recurs
State transitions
Alerts flow through states based on both user actions and system events:
┌─────────────────────────────────────────────────────┐
│ │
│ ┌──────────┐ ┌──────────────┐ │
│ │ │ User resolves │ │ │
│ │ Open │ ───────────────► │ Resolved │ │
│ │ │ │ │ │
│ └──────────┘ └──────────────┘ │
│ ▲ │ │
│ │ │ │
│ │ Issue recurs │ │
│ └─────────────────────────────────┘ │
│ │
└─────────────────────────────────────────────────────┘Opening an alert
Alerts are opened when:
- Chat detects a new issue and calls
trigger_alert - A previously resolved alert's underlying issue recurs (depending on deduplication settings)
Resolving an alert
Alerts can be resolved through:
- Dashboard: Click the resolve button on the alert card or in the alert thread
- Slack: Use the inline "Resolve" button on the alert notification
- API: Call the alert resolution endpoint programmatically
When you resolve an alert, Sazabi records who resolved it and when, providing an audit trail for incident review.