DEVOPS
Retire feature flags with zero evaluation traffic
Checks Datadog flag-evaluation metrics on a schedule and, for any flag that has logged zero evaluations over the observation window.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires
- ActionQuery flag evaluation countsDatadog
- LogicIsolate flags with zero evaluations all window
- ActionCreate Linear cleanup issue with evidenceLinear
- OutputOpen linked draft removal PRGitHub
What it does
Uses real production telemetry to decide which flags are dead. Instead of guessing from code age, it reads Datadog flag-evaluation counters: any flag that has not been evaluated a single time across the lookback window is treated as truly abandoned and queued for retirement.
When to use it
When your flags emit evaluation metrics and you want removal decisions backed by usage data, not assumptions. Best for mature platforms where a flag with zero traffic is a strong, defensible signal that it is safe to delete.
How it works
- 1A daily schedule starts the check.
- 2A Datadog query pulls evaluation counts per flag over the lookback window.
- 3A logic step isolates flags with exactly zero evaluations for the full window.
- 4For each dead flag, a Linear issue is created in the platform-hygiene project with the metric evidence attached.
- 5A GitHub action opens a draft removal PR linked to that Linear issue so the owner can finish and merge it.
Set it up
What you configure once, before turning it on.
- 1Connect DatadogMetrics, traces, log search.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect GitHubRepos, issues, pull requests, actions.
- 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.