Incident management process diagram
This is a worked example. Wavelength built the diagram below from the description on this page. Nobody drew it by hand.
What was said
Datadog detects an error spike and triggers an alert in PagerDuty. PagerDuty pages the on-call engineer. The on-call engineer opens an incident channel in Slack. If the incident is severity one, the incident commander joins and the status page is updated. The engineer fixes the problem, and afterward the team writes a postmortem in Confluence.
The diagram
What is in this flow
- Systems: Datadog, PagerDuty, Slack, Status Page and Confluence.
- People and teams: On-Call Engineer, Incident Commander and Team.
- Decisions: Severity One?.
- Size: 11 steps and 10 connections.
Questions to confirm
The AI inferred these links. On a real call, you ask the customer to confirm them.
- Does Severity One? fixes Fix Problem?
- Does Fix Problem postmortem Team?
Mermaid code
Copy this into any Markdown file, GitHub README, or Mermaid Live to render the same flow.
flowchart TD
n1(["Error Spike Detected")]
n2{{"Datadog"}}
n3{{"PagerDuty"}}
n4("On-Call Engineer")
n5{{"Slack"}}
n6{"Severity One?"}
n7("Incident Commander")
n8{{"Status Page"}}
n9("Team")
n10{{"Confluence"}}
n11["Fix Problem"]
n1 -->|detects error spike| n2
n2 -->|triggers alert| n3
n3 -->|pages| n4
n4 -->|opens incident channel| n5
n5 -->|evaluate severity| n6
n6 -->|Yes| n7
n7 -->|updates| n8
n6 -.->|fixes| n11
n11 -.->|postmortem| n9
n9 -->|writes postmortem| n10Map your own process
Describe your version out loud, or paste the transcript of a call. Wavelength draws the flow as you talk, and you can edit it by voice, by prompt, or by hand.
Every new account starts with 14 days of Pro. No card needed.