Notification Log
Read-only log of all notification dispatch attempts. Each row represents one notification sent (or attempted) to a channel. Shows delivery status (sent, failed, exhausted), retry attempts, error details, and timestamps. The notification queue also serves as the immutable audit trail for all alarm notifications. Entries are retained for 90 days.
Fields & columns
| Name | Description |
|---|---|
Time | When the notification was enqueued |
Severity | Alarm severity at the time of the transition |
Transition | What state change triggered the notification (opened, bumped, acknowledged, resolved) |
Summary | Alarm summary text |
Channel | Which channel the notification was sent to |
Status | Delivery status: pending, processing, sent, failed, or exhausted |
Attempts | Number of delivery attempts made |
Error | Error message from the last failed attempt (if any) |
Gotchas
- The notification log is read-only and cannot be modified through the API.
- Failed notifications are retried with exponential backoff: 30s, 60s, 120s, 240s, 480s.
- After 5 failed attempts, a notification is marked "exhausted" and will not be retried.
- Log entries older than 90 days are automatically purged (only terminal statuses: sent, exhausted).
- The 24h stats at the top refresh every 30 seconds automatically.
API calls (2)
| Method | Path | Description |
|---|---|---|
| GET | /api/health/alerting/notification-log | Query notification history with optional filters (status, channelId, alarmId) |
| GET | /api/health/alerting/notification-log/stats | Get 24h delivery statistics (sent, pending, failed, exhausted counts) |
Related
- Notification Channels — Channels are the delivery targets shown in the log
- Notification Policies — Policies determine which alarms create log entries
- Alarms — Each log entry corresponds to an alarm state transition