DEVOPS
Escalate flaky-test spikes that block deploys to PagerDuty
When Datadog detects a sudden surge in flaky failures on the main branch, checks whether deploys are blocked; if so, pages the on-call engineer via PagerDuty and posts a war-room…
How it runs
The automated pipeline, trigger to output.
- TriggerDatadog monitor: main-branch flake spikeDatadog
- ActionCheck deploy pipeline blocked status
- LogicDeploys blocked and above incident threshold?
- ActionCreate PagerDuty incident for CI on-callPagerDuty
- ActionOpen Slack war-room thread with top offendersSlack
- OutputLink incident and Datadog dashboard in threadSlack
What it does
Detects when flakiness crosses from annoyance into deploy-blocking incident. A Datadog monitor on main-branch flake rate triggers the flow, which confirms that the release pipeline is actually stalled, then escalates: it pages on-call through PagerDuty and opens a Slack war-room thread listing the tests driving the spike so the team can quarantine fast.
When to use it
Use this when a burst of new flakes can wedge your deploy pipeline and you need humans engaged in minutes, not at the next standup. It separates routine flake noise from true delivery-blocking events.
How it works
- 1A Datadog monitor alert fires on a main-branch flake-rate spike.
- 2The flow checks the deploy pipeline status to confirm releases are blocked, not merely slowed.
- 3A branch decides severity: page only if deploys are blocked and the spike exceeds the incident threshold.
- 4It creates a PagerDuty incident assigned to the CI on-call rotation.
- 5It opens a Slack war-room thread with the top offending tests and their failure counts.
- 6The final step links the PagerDuty incident and Datadog dashboard into the Slack thread for the responder.
Set it up
What you configure once, before turning it on.
- 1Connect DatadogMetrics, traces, log search.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More DevOps workflows
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.
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.
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.
Open a Zoom war-room from a Datadog multi-alert storm
When a Datadog monitor crosses a critical threshold, this workflow dedupes against active incidents, and only for a genuinely new outage it creates a Zoom bridge.
Auto-spin a Zoom war-room when PagerDuty hits SEV-1
When a PagerDuty incident escalates to a critical severity, this workflow creates a dedicated Zoom meeting and posts the bridge link to the incident's Slack channel so responders…
Spin up a war-room on demand from a Slack slash command
When an engineer runs a Slack command, this workflow creates a Zoom bridge, opens a tracking Sentry-linked incident, files a Linear issue for follow-up.
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.