ENGINEERING
SLO Exhaustion Forecaster from Datadog Burn Rate
Every hour, reads the current Datadog SLO burn rate, projects when the remaining error budget will hit zero at that pace.
How it runs
The automated pipeline, trigger to output.
- TriggerHourly schedule
- ActionFetch SLO status and burn rateDatadog
- LogicProject exhaustion date and set verdict
- OutputPost forecast to SlackSlack
What it does
This workflow turns a raw Datadog burn rate into a plain-English answer to the question every on-call lead asks: "If we keep burning at this rate, when do we run out of budget?" It pulls the SLO's current status and remaining budget, computes the projected exhaustion date, and reports it on a schedule so the team sees the trend before it becomes a crisis.
When to use it
Run this when you own one or more service-level objectives in Datadog and want a continuous, readable forecast instead of staring at burn-rate graphs. It is ideal for weekly reliability reviews and for catching slow leaks that a spike-only alert would miss.
How it works
- 1An hourly schedule fires the workflow.
- 2It queries the Datadog SLO API for the target objective's remaining budget and the trailing burn rate over the SLO window.
- 3A logic step projects the exhaustion timestamp: remaining budget divided by current burn rate, and assigns green (no exhaustion in window), amber (exhausts within the window), or red (already exhausted).
- 4It posts a Slack message with the projected date, days remaining, and verdict color.
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 Engineering workflows
Gate breaking API PRs behind downstream consumer acknowledgement
When a PR introduces a breaking contract change, comments the impact summary back on the PR, applies a blocking label.
Publish a versioned API changelog to Confluence on each release tag
On a new semver release tag, gathers the contract changes since the last release and writes a clean.
Agent reviews model-license fit and suggests compliant swaps on the PR
When a PR adds a Hugging Face model, an agent reads the model card and license, judges fit against your commercial-use policy.
Upgrade Impact Router to Module Code Owners
Maps a dependency-bump PR's affected modules to their CODEOWNERS, then DMs each owner on Slack with only the changelog slice that touches code they own.
Re-Voice IVR Prompts on Phone-Tree Config Merge
When a phone-tree config change merges in GitHub, regenerates the ElevenLabs audio for any prompt whose script changed in the diff and opens a follow-up PR adding the new audio…
Upstream Release to Notion Upgrade Brief
When a watched package publishes a new release, fetches the release notes, maps them to the internal modules that depend on it.
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.