Land in the war room with the dashboard already pulled

Forward the page to Carly and you'll land in the war room with context already on the thread — Datadog pulled, traffic correlated, hypothesis posted in #incidents. Triage in 30 seconds, not 10 minutes.

PagerDuty Datadog Slack

What Carly does

1. 01 Acknowledge the PagerDuty alert
2. 02 Pull the relevant Datadog dashboard for the affected service
3. 03 Correlate the metric spike with recent traffic or deploys
4. 04 Start a war-room thread in #incidents
5. 05 Post the initial hypothesis and suggested runbook step

Triage in 30 seconds, not 10 minutes

You land in the war room with context already on the thread. Stakeholders see a hypothesis instead of silence. The fix starts while the alert is still fresh.

Email this to Carly to kick it off.

Hey Carly,

A PagerDuty alert just fired and I need you to take first pass on triage. Acknowledge it, then pull the matching Datadog dashboard for the affected service and look for whether the spike lines up with recent traffic or a deploy.

Start a war-room thread in #incidents, drop the dashboard link in, and post your initial hypothesis plus the runbook step you'd try first. Check with me before paging anyone else or running any commands against the service.

Thanks!

More recipes for it & security teams

Investigate a Sentry error spike

Find the deploy, identify the file, file the fix, ping the team channel.

Read →

Assemble compliance evidence for an audit

Pull access reviews and WAF configs into a Notion evidence pack for the auditor.

Read →

Onboard a new employee's access

Provision Auth0 groups, share Bitwarden collections, add to the right Slack channels.

Read →