Alert Inbox Triage #
The Alert Inbox (/v1/platform/alerts) aggregates deduplicated infrastructure and mail pipeline alerts without exposing tenant PII or message payloads.
Alert Lifecycle & Actions #
| State | Meaning | Operator Action |
|---|---|---|
open | Active unacknowledged condition | Investigate root cause; acknowledge to claim ownership |
acknowledged | Operator actively investigating | Continue remediation or snooze during scheduled work |
snoozed | Notification noise temporarily muted | Auto-reopens when snooze timer expires unless resolved |
resolved | Underlying fault verified cleared | Closes incident with resolution note |
Health Impact Invariant #
IMPORTANT
Snoozing an alert only silences notification noise; it NEVER marks a degraded service healthy. The Service Topology health indicator continues to report degraded or unhealthy until the underlying probe passes and the alert is resolved.
API Operations #
- List Alerts:
GET /v1/platform/alerts(supports filtering and pagination). - Inspect Alert:
GET /v1/platform/alerts/:id. - Acknowledge / Snooze / Resolve:
POST /v1/platform/alerts/:id/acknowledgePOST /v1/platform/alerts/:id/snoozePOST /v1/platform/alerts/:id/resolve
All mutating alert actions require platform.alerts.mutate, a unique request key (platformAlertsRequestKeyPattern), and are recorded in the platform audit log.