ENGINEERING
Escalate Sustained SLO Burn to PagerDuty After Failed Gates
When a service's PR gate fails repeatedly within a window, confirms sustained Honeycomb burn and pages the on-call via PagerDuty with the burn math and links to the blocked PRs.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook: PR gate recorded a failureHTTP webhook
- LogicCount failures in window; proceed past threshold
- ActionConfirm sustained burn via HoneycombHoneycomb
- ActionOpen PagerDuty incident with burn math and PR linksPagerDuty
- OutputRoute incident to service on-call policyPagerDuty
What it does
Turns repeated gate failures into a real page. When the burn-rate gate blocks merges to the same service multiple times inside a short window, this flow re-checks Honeycomb to confirm the burn is sustained (not a transient spike), then opens a PagerDuty incident addressed to that service's on-call. The incident body carries the burn multiplier, budget remaining, and links to the PRs currently being blocked so responders have full context immediately.
When to use it
Use it when a hot SLO is blocking shipping and nobody has acknowledged it. It bridges the silent gate-failure state into an actionable page, so a burning budget doesn't quietly stall a team for hours.
How it works
- 1A webhook fires each time the PR gate records a failure for a service.
- 2A logic step counts failures for that service within the window and proceeds only past the threshold.
- 3It re-queries Honeycomb to confirm the burn is sustained across windows.
- 4It opens a PagerDuty incident with the burn math and blocked-PR links.
- 5The incident routes to the service's on-call escalation policy.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect HoneycombDistributed traces and queries.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 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.