ENGINEERING
Escalate to PagerDuty when Datadog multi-window burn rate exhausts budget
Evaluates Datadog SLO burn rate across both fast and slow windows on a schedule, and when both windows agree the budget is being exhausted it opens a PagerDuty incident…
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule fires every few minutes
- ActionQuery Datadog SLO burn rate (fast + slow windows)Datadog
- LogicRequire both windows over threshold
- ActionOpen PagerDuty incident for the servicePagerDuty
- OutputNotify on-call Slack channel with incident linkSlack
What it does
This workflow runs the classic multi-window, multi-burn-rate SLO evaluation against Datadog on a fixed cadence. It only escalates when both the short window and the long window confirm sustained budget burn, which suppresses the false alarms that single-window alerts produce. On confirmation it opens a PagerDuty incident and pings the on-call Slack channel.
When to use it
Use this when you want SLO-driven paging rather than threshold-on-a-graph paging, and your SLOs live in Datadog. It is ideal for services where noisy single-window alerts have caused alert fatigue.
How it works
- 1A schedule trigger fires every few minutes.
- 2The workflow queries the Datadog SLO API for the service's burn rate over the fast window and the slow window.
- 3A logic step requires both windows to exceed their respective burn thresholds before proceeding, otherwise it exits quietly.
- 4When both agree, it opens a PagerDuty incident tagged with the service and remaining budget.
- 5It posts the incident link and burn details to the on-call Slack channel for visibility.
Set it up
What you configure once, before turning it on.
- 1Connect DatadogMetrics, traces, log search.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 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.