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

πŸ› οΈ DevOps & SRE Β· Sequence

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.

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

  • The status page is updated early, not after the fix
  • An incident commander coordinates, others investigate
  • Rollback is the first option when a deploy caused it

Prompt used

Incident response sequence: monitoring detects a spike in errors and PagerDuty pages the on-call engineer, who acknowledges and opens a Slack incident channel. The incident commander updates the status page. The engineer checks dashboards, finds the latest deploy caused it and rolls back through the CD tool. Error rates recover, the status page is updated to resolved and a postmortem is scheduled.

Mermaid code
sequenceDiagram
  participant MON as Monitoring
  participant PD as PagerDuty
  actor OC as On-call Engineer
  participant SL as Slack Incident Channel
  actor IC as Incident Commander
  participant SP as Status Page
  participant CD as CD Tool
  MON->>PD: Error rate above 5%
  PD->>OC: Page
  OC->>PD: Acknowledge
  OC->>SL: Open incident channel
  SL->>IC: Commander joins
  IC->>SP: Investigating - checkout errors
  OC->>MON: Check dashboards
  MON-->>OC: Started after 14:05 deploy
  OC->>CD: Roll back to previous version
  CD-->>OC: Rollback done
  MON-->>SL: Error rate normal
  IC->>SP: Resolved
  IC->>SL: Schedule postmortem

Inside this diagram

A sequence diagram with 7 participants and 13 messages, in the order they happen.

People

  • On-call Engineer
  • Incident Commander

Systems

  • Monitoring
  • PagerDuty
  • Slack Incident Channel
  • Status Page
  • CD Tool

Steps in order

  • 1. Monitoring β†’ PagerDuty: Error rate above 5%
  • 2. PagerDuty β†’ On-call Engineer: Page
  • 3. On-call Engineer β†’ PagerDuty: Acknowledge
  • 4. On-call Engineer β†’ Slack Incident Channel: Open incident channel
  • 5. Slack Incident Channel β†’ Incident Commander: Commander joins
  • 6. Incident Commander β†’ Status Page: Investigating - checkout errors
  • 7. On-call Engineer β†’ Monitoring: Check dashboards
  • 8. Monitoring β†’ On-call Engineer: Started after 14:05 deploy (reply)
  • 9. On-call Engineer β†’ CD Tool: Roll back to previous version
  • 10. CD Tool β†’ On-call Engineer: Rollback done (reply)
  • 11. Monitoring β†’ Slack Incident Channel: Error rate normal (reply)
  • 12. Incident Commander β†’ Status Page: Resolved
  • 13. Incident Commander β†’ Slack Incident Channel: Schedule postmortem

Make your own diagram like this

Describe your own system in plain English and the AI sequence diagram generator draws it in seconds, in the same style as this template.

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.

State MachineDevOps & SRE

Incident Lifecycle

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

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.