DEVOPS
Retire Zero-Traffic Feature Flags Using Datadog Eval Metrics
Checks Datadog for flag-evaluation metrics and finds flags that haven't been evaluated in 30 days, then files a Linear removal ticket for each truly-dead flag.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled harvester run
- ActionQuery Datadog for per-flag evaluation countsDatadog
- LogicKeep flags with zero evaluations in 30 days
- ActionConfirm flag still exists in registryPostgres
- OutputFile Linear retirement ticket per dead flagLinear
What it does
Queries Datadog for per-flag evaluation counts, identifies flags that have received zero evaluations over the trailing 30 days, and opens a Linear ticket to retire each one. This catches flags that are dead in practice even if their kill-date hasn't arrived.
When to use it
Use this when kill-dates aren't reliable but you do emit a metric every time a flag is evaluated. Traffic-based detection is the most honest signal that a flag is safe to remove, since it proves no code path still depends on it.
How it works
- 1A scheduled run triggers the harvester.
- 2It queries Datadog for the `feature_flag.evaluations` metric grouped by flag key over the last 30 days.
- 3A logic step keeps only flags with a total evaluation count of zero.
- 4For each zero-traffic flag it cross-checks the registry in Postgres to confirm the flag still exists and isn't newly created.
- 5It creates a Linear issue per confirmed dead flag with the last-seen date and owning team, ready for an engineer to action.
Set it up
What you configure once, before turning it on.
- 1Connect DatadogMetrics, traces, log search.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect LinearIssues, projects, cycles, triage.
- 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.