DEVOPS
Hourly Datadog error-budget burn digest to Slack
Every hour, pulls each service's SLO status and burn rate from Datadog and posts a single ranked Slack digest showing remaining budget and which services are burning fast enough…
How it runs
The automated pipeline, trigger to output.
- TriggerHourly schedule
- ActionFetch Datadog SLO status + burn ratesDatadog
- LogicCompute remaining budget + time-to-exhaustion
- LogicRank services worst-first
- OutputPost ranked digest to SlackSlack
What it does
Gives the team one tidy hourly readout of error-budget health across all your tracked SLOs. It reads Datadog SLO status and short-window burn rates, computes time-to-exhaustion per service, and posts a ranked Slack message so on-call sees trouble before it becomes an incident.
When to use it
Use it when you manage many SLOs in Datadog and want proactive visibility instead of waiting for a monitor to page. Good for platform teams running a shared #reliability channel.
How it works
- 1A schedule fires once per hour.
- 2The flow fetches SLO status objects and current burn rates from Datadog for the configured SLO IDs.
- 3A logic step computes remaining budget and projected exhaustion time, then flags any service burning faster than the window allows.
- 4It sorts services worst-first and formats a compact digest with budget percentages and burn multipliers.
- 5The digest posts to the chosen Slack channel; if nothing is at risk it can post a brief all-clear line.
Set it up
What you configure once, before turning it on.
- 1Connect DatadogMetrics, traces, log search.
- 2Connect SlackChannels, DMs, threads, mentions.
- 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
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-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…
Page on-call when a Hugging Face Space build is stuck or errored
Polls Hugging Face Space runtime status on a schedule and opens a PagerDuty incident when a Space sits in a build or error state past a deadline, with a Slack heads-up.
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.
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.
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.