ENGINEERING
Freeze risky merges when Honeycomb SLO burn rate spikes
Watches a Honeycomb SLO burn-rate alert and, when it crosses your fast-burn threshold, applies a merge-freeze label to open GitHub PRs touching the affected service and posts…
How it runs
The automated pipeline, trigger to output.
- TriggerHoneycomb SLO burn-rate alert webhookHoneycomb
- LogicCheck 1-hour burn rate against fast-burn threshold
- ActionFind open GitHub PRs touching the affected serviceGitHub
- ActionApply merge-freeze label to matching PRsGitHub
- OutputPost freeze notice with burn rate and held PRs to SlackSlack
What it does
Turns a Honeycomb SLO burn-rate alert into an automatic, scoped merge freeze. When the error budget starts burning faster than your safe rate, this stops new risky code from landing on the at-risk service until the budget recovers.
When to use it
Run this when you trust Honeycomb SLOs as your reliability source of truth and want budget burn to gate merges automatically, instead of relying on an on-call engineer to remember to halt deploys mid-incident.
How it works
- 1A Honeycomb burn-alert webhook fires when the fast-burn budget rate trips.
- 2The flow reads the alert payload and checks whether the 1-hour burn rate exceeds your configured threshold (e.g. 14.4x).
- 3If under threshold, it exits quietly so normal alert noise does not freeze anything.
- 4If over, it queries open GitHub PRs labeled or pathed to the affected service and applies a `merge-freeze` label plus a status note.
- 5It posts a freeze announcement to the team Slack channel with the SLO name, current burn rate, and which PRs were held.
Set it up
What you configure once, before turning it on.
- 1Connect HoneycombDistributed traces and queries.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 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.