incident lifecycle
The stages of an incident: detection, declaration, mitigation, end of user impact and closure.
In more detail
Naming each stage gives separate clocks. Each clock suggests a different improvement: better alerting shortens detection, a clearer escalation path shortens declaration, and a safer mitigation shortens user impact.
Example
time to detect 1 minutes, time to declare 7, time to mitigate 42, user impact 66, incident length 89Related terms
- detection — The moment a team learns of a symptom, usually from an alert or a user report.
- incident declaration — Formally starting coordinated incident response, including naming an incident commander.
- mitigation — An action that stops or limits harm to users, such as a rollback or routing traffic around a failure, even before the cause is fixed.
- incident closure — Formally ending an incident after the service has stayed healthy for an agreed period and follow-up work has an owner.
Taught in
- On-Call And Incident Response — DevOps & Site Reliability Engineering
- The Incident Lifecycle — DevOps & Site Reliability Engineering