CloudSketch AI Logo
FeaturesTemplatesPricingEnterpriseAboutContactLog in
πŸŒ™β˜€οΈ
Log inStart free
Home/Templates/DevOps & SRE

πŸ› οΈ DevOps & SRE Β· State Machine

Incident Lifecycle

The stages of a production incident from the first alert to the postmortem, with severity escalation along the way.

More DevOps & SRE templates

Opening a template is free and never counts toward your daily diagrams. Asking the AI to change it counts as one.

Drawing diagram…

What this diagram shows

  • Acknowledging an alert starts the response clock
  • Incidents can be escalated to a higher severity
  • Every major incident ends with a blameless postmortem

Prompt used

State machine for an incident: Triggered by an alert, Acknowledged by on-call, Investigating, Escalated if severity rises, Mitigated when users are no longer affected, Resolved when the root cause is fixed, then PostmortemDone. False alarms are closed right after acknowledgement.

Mermaid code
stateDiagram-v2
  [*] --> Triggered: Alert fires
  Triggered --> Acknowledged: On-call responds
  Triggered --> Escalated: No ack in 10 minutes
  Acknowledged --> Investigating
  Acknowledged --> Closed: False alarm
  Investigating --> Escalated: Severity raised
  Escalated --> Investigating: More responders join
  Investigating --> Mitigated: Users no longer affected
  Mitigated --> Resolved: Root cause fixed
  Resolved --> PostmortemDone: Review published
  PostmortemDone --> [*]
  Closed --> [*]

Inside this diagram

A state diagram with 8 states and 9 transitions.

States

  • Triggered
  • Acknowledged
  • Escalated
  • Investigating
  • Closed
  • Mitigated
  • Resolved
  • PostmortemDone

Starts in

  • Triggered

Ends in

  • PostmortemDone
  • Closed

Transitions

  • Triggered β†’ Acknowledged when On-call responds
  • Triggered β†’ Escalated when No ack in 10 minutes
  • Acknowledged β†’ Investigating
  • Acknowledged β†’ Closed when False alarm
  • Investigating β†’ Escalated when Severity raised
  • Escalated β†’ Investigating when More responders join
  • Investigating β†’ Mitigated when Users no longer affected
  • Mitigated β†’ Resolved when Root cause fixed
  • Resolved β†’ PostmortemDone when Review published

Make your own diagram like this

Describe your own system in plain English and CloudSketch AI draws it in seconds. See all AI diagram generators.

Related templates

FlowchartDevOps & SRE

GitOps Deployment Flow

How a code change reaches production with GitOps: CI builds and tests, the image tag is written to a config repo, and Argo CD syncs the cluster to match Git.

C4 ArchitectureProDevOps & SRE

Observability Stack (Metrics, Logs, Traces)

A complete observability setup: OpenTelemetry collects metrics, logs and traces from services, which are stored separately and viewed together in Grafana with alerting.

SequenceDevOps & SRE

Incident Response Sequence

Who does what when production breaks: monitoring pages the on-call engineer, an incident channel is opened, customers are updated and the fix is rolled out.

DeploymentProDevOps & SRE

Blue-Green Deployment

A blue-green setup where a new version is deployed next to the live one and traffic is switched only after it passes checks, allowing instant rollback.

FlowchartDevOps & SRE

Infrastructure as Code Pipeline

How infrastructure changes are made safely with Terraform: plan on pull request, policy checks, approval, apply and drift detection.

C4 ArchitectureProDevOps & SRE

Internal Developer Platform

A self-service platform for developers: a Backstage portal with templates that create repos, pipelines and environments without tickets to the ops team.