DEVOPS
Weekly Noisy-Alert and On-Call Load Audit
On a weekly schedule, pull Datadog alert volume and PagerDuty incident history, have an agent flag noisy monitors and overloaded rotations, and file tuning tasks in Linear.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires
- ActionQuery Datadog alert volume and flap rate per monitorDatadog
- ActionPull PagerDuty incident and on-call load dataPagerDuty
- LogicAgent ranks noisy monitors and overloaded rotations
- ActionFile tuning tasks in Linear by owning teamLinear
- OutputPost on-call load digest to SlackSlack
What it does
Runs a weekly hygiene review of your alerting. It aggregates Datadog alert frequency and PagerDuty incident and acknowledgement data, then an agent identifies the noisiest monitors, the most-paged rotations, and after-hours load. It files concrete tuning recommendations as Linear tasks and posts a digest to Slack so alert fatigue gets managed proactively.
When to use it
Use it when on-call burnout and alert fatigue are creeping in and you want a recurring, data-driven review that turns noise into a prioritized backlog instead of an anecdote.
How it works
- 1A weekly schedule triggers the audit.
- 2Datadog is queried for alert counts and flap frequency per monitor over the past week.
- 3PagerDuty incident, acknowledgement, and escalation data is pulled per rotation, including off-hours pages.
- 4An agent ranks the noisiest monitors and most-loaded rotations and writes specific tuning recommendations.
- 5Linear tasks are created for each high-priority tuning item, assigned to the owning team.
- 6A summary digest with the top offenders and trends is posted to Slack.
Set it up
What you configure once, before turning it on.
- 1Connect DatadogMetrics, traces, log search.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Connect LinearIssues, projects, cycles, triage.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More DevOps workflows
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.
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.
Generate a weekly de-flake report and assign Linear cleanup tickets
On a weekly schedule, aggregates the current quarantine manifest and recent flake history, builds a prioritized report.
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.
Auto-release tests from quarantine once they prove stable
Triggered by a webhook from a nightly stability runner, checks whether quarantined tests have passed enough consecutive runs, removes the stable ones from quarantine in GitHub.
Quarantine a test on demand from a PR comment command
Triggered when an engineer comments a quarantine command on a pull request, validates the test name, commits the quarantine change to that PR branch, opens a tracking issue.
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.