Trace a spike to the deploy in 30 seconds

Drop the Sentry link to Carly and get the deploy, the file, and the rollback command back in 30 seconds — instead of a Slack thread full of speculation.

Sentry GitHub Slack

What Carly does

1. 01 Fetch the Sentry issue — stack trace, frequency, users affected
2. 02 List recent deploys in the affected service
3. 03 Correlate the spike start with deploy timestamps
4. 04 Identify the file:line from the stack that changed in that deploy
5. 05 Post a heads-up in the team channel with the rollback command

Root-cause traced in 30 seconds

The engineer on-call sees the deploy, the file, and the rollback option immediately. Rollbacks happen in minutes — not after a Slack thread full of speculation.

Email this to Carly to kick it off.

Hey Carly,

Sentry is showing a spike on /api/charge in the payments service. Pull the issue from Sentry — stack trace, frequency, users affected — and list the last few deploys to that service. Line up the spike start time with the deploy timestamps so we know which one to suspect.

From the top of the stack, find the file and line that changed in that deploy and post a heads-up in #eng-payments with the suspected commit and the rollback command. Don't run the rollback yet — wait for me to confirm.

Thanks!

More recipes for it & security teams

Triage a PagerDuty alert

Pull Datadog, correlate with traffic, start a war room in #incidents.

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 →