DEVOPS
Quarantine Tests Crossing a Datadog Flake-Rate Threshold
Runs on a schedule, queries Datadog CI Visibility for each test's flaky-rate metric.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule
- ActionQuery Datadog CI Visibility flake ratesDatadog
- LogicFilter tests over threshold, not yet quarantined
- ActionOpen GitHub quarantine PR with skip annotationGitHub
- ActionPage owning team via PagerDutyPagerDuty
- OutputDeliver quarantine summary
What it does
This workflow uses real flake-rate telemetry rather than a single rerun. It polls Datadog CI Visibility for per-test flakiness over a rolling window and, for any test exceeding your tolerance, opens a quarantine PR that marks the test skipped and alerts the owning team.
When to use it
Use this when you already ship test results to Datadog and want a data-driven quarantine policy — e.g. any test flaking more than 5% over 7 days gets pulled from the blocking path until fixed, with on-call notified.
How it works
- 1A scheduled trigger fires nightly.
- 2The flow queries Datadog CI Visibility for each test's flaky-rate over the trailing window.
- 3A logic step filters to tests above the configured threshold that are not already quarantined.
- 4For each, it opens a GitHub PR adding a skip/quarantine annotation and a comment with the flake-rate evidence.
- 5It pages the owning team through PagerDuty with the test name, rate, and PR link.
- 6A summary of all quarantined tests is delivered as the final output.
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.
- 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.