Incidents and post-mortems
Confirmed incidents
Section titled “Confirmed incidents”A quorum-confirmed failure opens an incident with its start at the confirmation second. Every event lands on the timeline: region votes, notifications, acknowledgment, recovery. Linked status-page components and the curated availability record use this timeline.
Manual incidents
Section titled “Manual incidents”Open an incident by hand for anything your customers notice, with or without a bound monitor. Curate it, then publish it explicitly to the status pages you choose, because publishing is always your own step. Manual incidents are included from Sentinel, and automatic incidents and acknowledgment are available on every plan.
Post-mortems and action items
Section titled “Post-mortems and action items”Writing and publishing post-mortems is part of incident command, included from Sentinel like opening incidents by hand. Automatic, quorum-confirmed incidents open on every plan, and incident command adds the manual work on top of them.
A post-mortem attaches to the incident: impact, root cause, lessons, plus action items with owners. It moves from draft to published in an explicit step, internal or public. Each post-mortem has its own address in the app, so it can be linked from a ticket or a report.
Saving and publishing are separate steps. You write in private, publish with its own action, and choose separately whether the result is internal or public.
Every change appears in version history with the actor, time, and action, such as save, publish, or restore. Restoring an earlier state creates another history entry, and the activity log records the affected fields, so the history stays attributable and reversible. Post-mortem versions follow an object-specific lifecycle, described under evidence and retention together with the way to confirm binding retention terms.
Acknowledgment and ownership
Section titled “Acknowledgment and ownership”Acknowledging takes the incident: escalation stops, other devices quiet down, reminders address the owner. The acknowledgment timestamp is part of the record, which is why the escalation ladder ends in an acknowledged incident, not in silence.
- Status pages: share incidents with your customers.
- Evidence and retention: how incidents become SLA figures.