DEVOPS
Page on-call when Datadog CI build-duration anomaly maps to a cache miss
Triggers on a Datadog CI pipeline duration anomaly, confirms it correlates with a build-cache miss rate spike.
How it runs
The automated pipeline, trigger to output.
- TriggerDatadog CI duration anomaly webhookDatadog
- ActionQuery cache miss-rate metric for same windowDatadog
- LogicDuration jump correlated with cache miss spike?
- ActionAssemble incident payload with both signals
- OutputOpen PagerDuty incident for CI on-callPagerDuty
What it does
When Datadog detects an anomalous jump in CI pipeline duration, this flow checks whether the slowdown lines up with a spike in cache miss rate. If both are true, it opens a PagerDuty incident pre-filled with the affected pipeline, the duration delta, and the cache metrics so on-call starts with context instead of a blank page.
When to use it
Use it for teams that already monitor CI in Datadog and want to separate real cache regressions from ordinary build-time noise. Duration alone is noisy; gating on a correlated cache-miss spike removes the false pages from flaky tests or runner contention.
How it works
- 1A Datadog monitor webhook fires on a CI pipeline duration anomaly.
- 2The flow queries Datadog for the cache miss-rate metric over the same interval.
- 3A branch checks whether miss rate is elevated alongside the duration jump.
- 4If correlated, it builds an incident payload with both signals and the pipeline link.
- 5It opens a PagerDuty incident and routes it to the CI on-call escalation.
- 6If not correlated, it logs the event and exits quietly.
Set it up
What you configure once, before turning it on.
- 1Connect DatadogMetrics, traces, log search.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.