ENGINEERING
Weekly Error-Budget Digest to Confluence
Each Monday, this workflow rolls up burn rate and remaining budget across all tracked Datadog SLOs, ranks services by exhaustion risk.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly Monday schedule
- ActionFetch all SLOs and burn ratesDatadog
- LogicRank services by exhaustion risk
- ActionPublish digest pageConfluence
- OutputLink digest in SlackSlack
What it does
It produces the weekly reliability report a manager would otherwise assemble by hand. It gathers every tracked SLO's remaining budget and burn rate, computes a projected exhaustion date per service, sorts the fleet from most-at-risk to healthiest, and publishes a clean Confluence page the team can review and link to.
When to use it
Use it when you run reliability reviews across many services and want a single source-of-truth page each week instead of scattered dashboards. It is reporting, not paging, so it summarizes the whole portfolio rather than reacting to one alert.
How it works
- 1A weekly Monday schedule starts the run.
- 2It fetches the list of SLOs and each one's remaining budget and trailing burn rate from Datadog.
- 3A logic step computes projected exhaustion per service and ranks them by risk, tagging any projected to exhaust this week.
- 4It renders a digest with a ranked table, week-over-week deltas, and the at-risk callouts.
- 5It publishes or updates the dated Confluence page and links it in Slack.
Set it up
What you configure once, before turning it on.
- 1Connect DatadogMetrics, traces, log search.
- 2Connect ConfluenceSpaces, pages, blueprints.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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 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.