Solution skill
Incident response: declare fast, timeline everything, postmortem with data
Complete solution
Shows how to fix incident response: declare fast, timeline everything, postmortem with data. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
Run a game day: declare a test incident, page the on-call from it, confirm the timeline captures the Slack thread, and write the postmortem. Commander owns the incident, not the fix. Their job is coordination, timeline, and comms. The best engineer on the fix is not the commander.
When to use
You are seeing this: Declare from wherever you are: the alert that fired, a dashboard graph widget, the Incidents UI, or Slack with /datadog incident. Use this skill when you run into "Incident response: declare fast, timeline everything, postmortem with data".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Incident response workflow in Datadog
Declare fast
Declare from wherever you are: the alert that fired, a dashboard graph widget, the Incidents UI, or Slack with /datadog incident. The declaration needs three things: a descriptive title, a severity (SEV-1 most severe to SEV-5 least, customizable), and an incident commander. Fill all three at declaration; "we will assign a commander later" is how incidents drift.
Run it
- Commander owns the incident, not the fix. Their job is coordination, timeline, and comms. The best engineer on the fix is not the commander.
- Timeline everything: detection, actions, comms. The timeline is the postmortem draft and the legal record. Slack integration can mirror thread replies into the timeline.
- Page from the incident: the On-Call integration pages teams directly from the incident, manually or automatically. Escalate the page into the incident rather than running a parallel thread.
- Status pages: connect incidents to status pages for customer comms. One source of truth beats five Slack threads.
After
- Postmortem in notebooks: draft and review the postmortem where the data lives. The incident analytics (time to resolution, customer impact) feed the review with numbers, not vibes.
- Action items with owners: every postmortem ends with dated, owned actions. "Improve monitoring" is not an action item.
- Severity calibration: if everything is SEV-2, the scale is broken. Review severity distribution quarterly.
Verify
Run a game day: declare a test incident, page the on-call from it, confirm the timeline captures the Slack thread, and write the postmortem. The workflow you have not rehearsed is the workflow that fails at 3am.
Evidence
The Incident Management docs: declare an incident from a dashboard graph widget, the Incidents UI, or any alert reporting into Datadog; declaration needs title, severity (SEV-1 to SEV-5), and incident commander; integrates with On-Call to escalate pages and with Slack via /datadog incident. Verified against live docs 2026-09-26.
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_fOfDbTQMa24gTnMElqvM1w" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Incident response: declare fast, timeline everything, postmortem with data <span>— Vectle</span></a>