DEVOPS
Daily flaky-test rollup from Datadog CI Visibility to Linear
Each morning, queries Datadog CI Visibility for tests with a flake rate above threshold over the last 7 days and creates or updates a Linear issue per offending test.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule before standup
- ActionQuery Datadog CI Visibility for 7-day flake ratesDatadog
- LogicKeep tests above flake-rate threshold
- LogicExisting Linear issue for this test fingerprint?Linear
- ActionCreate or update Linear issue with metrics and priorityLinear
- OutputPost ranked top-10 rollup to Linear projectLinear
What it does
Pulls flaky-test metrics from Datadog CI Visibility on a daily schedule, identifies tests whose flake rate crossed the team's threshold over a rolling 7-day window, and turns each one into a tracked, prioritized Linear issue. Tests already tracked get their flake rate and re-run count updated instead of duplicated.
When to use it
Use this when flake data lives in Datadog but the work to fix it needs to live in your engineering backlog. It gives the team a daily, deduplicated, ranked list of the worst offenders instead of scattered alerts.
How it works
- 1A daily schedule fires before standup.
- 2The flow queries Datadog CI Visibility for test flake rate, re-run count, and wasted CI minutes over the trailing 7 days.
- 3A filter keeps only tests above the configured flake-rate threshold.
- 4For each, it checks Linear for an existing `flaky` issue keyed by the test fingerprint.
- 5Existing issues are updated with fresh metrics; new ones are created with priority derived from wasted developer minutes.
- 6The final step posts the ranked top-10 rollup to the team's Linear project description.
Set it up
What you configure once, before turning it on.
- 1Connect DatadogMetrics, traces, log search.
- 2Connect LinearIssues, projects, cycles, triage.
- 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.