ENGINEERING
SLO burn triggers ramp-down notice and PagerDuty page
When a Honeycomb SLO burn crosses the fast-burn threshold, opens a PagerDuty incident for the on-call and posts a customer-facing ramp-down notice to Slack so traffic can be shed…
How it runs
The automated pipeline, trigger to output.
- TriggerHoneycomb fast-burn SLO alertHoneycomb
- LogicClassify fast burn vs slow trend
- ActionOpen PagerDuty incident for on-callPagerDuty
- OutputPost ramp-down notice to SlackSlack
What it does
This is the incident-side companion to a merge freeze. A fast burn means you're about to blow the budget within the hour, so this workflow pages the service owner through PagerDuty and broadcasts a ramp-down notice telling the team to begin shedding non-critical traffic and pause risky rollouts.
When to use it
Use it for high-severity, fast-burn SLOs where the right human response is immediate — not just a code freeze, but active load shedding and an on-call engagement. Pair it with the merge-freeze workflow for full coverage.
How it works
- 1Honeycomb fires a fast-burn SLO alert into the workflow.
- 2The workflow checks whether the burn rate exceeds the fast-burn multiplier (e.g. 14x over 1 hour) versus a slower trend.
- 3If it's a fast burn, it opens a PagerDuty incident routed to the service's escalation policy with the burn detail attached.
- 4It posts a ramp-down notice to the incident Slack channel listing the affected service, projected time-to-exhaustion, and the recommended shedding steps.
Set it up
What you configure once, before turning it on.
- 1Connect HoneycombDistributed traces and queries.
- 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.