DEVOPS
Datadog Alert to Recent-Deploy Correlation and Rollback Page
On a Datadog service alert, the workflow checks GitHub for deploys in the last 30 minutes and, if a recent deploy lines up, pages on-call with a rollback recommendation instead…
How it runs
The automated pipeline, trigger to output.
- TriggerDatadog service alert firesDatadog
- ActionQuery GitHub for deploys in last 30 minutesGitHub
- LogicBranch on deploy correlation with alert window
- ActionPage PagerDuty with rollback recommendation or standardPagerDuty
- OutputPost correlation finding to SlackSlack
What it does
This workflow makes Datadog alerts smarter by correlating them with deploy timing. When a service alerts, it checks GitHub for any deploy to that service in the last 30 minutes. If a recent deploy lines up with the alert, it pages on-call with an explicit rollback recommendation and the suspect commit; if not, it routes the alert as a normal investigation.
When to use it
Use it when most of your incidents trace back to a recent deploy but responders still spend time confirming that. Best for teams shipping frequently who want the deploy-versus-alert correlation done automatically.
How it works
- 1A Datadog monitor alert fires for a specific service.
- 2The workflow queries GitHub for deployments to that service in the last 30 minutes.
- 3A branch checks whether a recent deploy correlates with the alert window.
- 4If correlated, it pages PagerDuty with the suspect commit, author, and a rollback recommendation.
- 5If not correlated, it pages PagerDuty as a standard investigation with the monitor link.
- 6The final step posts the correlation finding and suspect commit to Slack.
Set it up
What you configure once, before turning it on.
- 1Connect DatadogMetrics, traces, log search.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More DevOps workflows
Hugging Face Spaces idle-runtime sweep with auto-pause
On a schedule, scans all Hugging Face Spaces for ones running idle past a threshold, pauses them to stop billing, and posts a Slack summary with the estimated monthly savings.
Slack-approved pause for idle Hugging Face Spaces
On a daily scan it finds idle paid Spaces and posts an interactive Slack approval; on approve it pauses the Space and logs the decision to a GitHub issue audit trail.
Generate a weekly de-flake report and assign Linear cleanup tickets
On a weekly schedule, aggregates the current quarantine manifest and recent flake history, builds a prioritized report.
Block costly Hugging Face Space hardware upgrades in PR review
When a pull request changes a Space's hardware config, it estimates the new monthly cost and posts a GitHub PR comment that flags upgrades crossing a budget ceiling.
Auto-release tests from quarantine once they prove stable
Triggered by a webhook from a nightly stability runner, checks whether quarantined tests have passed enough consecutive runs, removes the stable ones from quarantine in GitHub.
Quarantine a test on demand from a PR comment command
Triggered when an engineer comments a quarantine command on a pull request, validates the test name, commits the quarantine change to that PR branch, opens a tracking issue.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.