ENGINEERING
Page on-call and lock the release branch on critical fast burn
When Honeycomb signals a critical fast-burn event, pages the on-call engineer via PagerDuty and enables branch protection that blocks merges to the release branch until budget…
How it runs
The automated pipeline, trigger to output.
- TriggerHoneycomb critical fast-burn alert webhookHoneycomb
- LogicConfirm alert is critical tier, not a warning
- ActionTrigger PagerDuty incident for on-call rotationPagerDuty
- ActionLock release branch via GitHub branch protectionGitHub
- OutputPost branch-lock and page notice to SlackSlack
What it does
Handles the worst-case burn: a critical fast-burn alert that means the budget will be exhausted within hours. It escalates to the on-call engineer and hard-locks the release branch so no further merges can compound the incident.
When to use it
Reserve this for your tightest, highest-severity SLOs where continuing to ship during a fast burn is unacceptable. It is the enforcement-with-teeth counterpart to softer label-based freezes.
How it works
- 1A Honeycomb critical fast-burn alert webhook fires.
- 2A logic step confirms the alert is the critical tier and not a lower-severity warning; warnings exit early.
- 3The flow triggers a PagerDuty incident for the owning service's on-call rotation with the SLO and burn rate.
- 4It updates GitHub branch protection on the release branch to require an admin override, effectively blocking merges.
- 5It posts a Slack alert stating the branch is locked, who was paged, and the conditions to unlock.
Set it up
What you configure once, before turning it on.
- 1Connect HoneycombDistributed traces and queries.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Connect GitHubRepos, issues, pull requests, actions.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Engineering workflows
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.
Block PRs that add incompatible Hugging Face model licenses
When a pull request adds or bumps a Hugging Face model dependency, it fetches the model card license, checks it against your org's allowed-license policy.
Quarterly Logging Hygiene Audit Agent
An agent-driven quarterly sweep that surveys all Axiom datasets, builds a logging-hygiene scorecard per service.
Post-Merge Log Volume Recheck After Downsampling PR
After a log-level PR merges, waits a day then re-queries Axiom to confirm the targeted stream's volume actually dropped.
Axiom Ingest Cost Spike to Linear Triage Ticket
When Axiom ingest volume spikes beyond its baseline, identifies which service caused it and files a Linear ticket with the offending log stream, sample lines, and a downsampling…
File a Linear license-review ticket for risky model adds
When a PR introduces a Hugging Face model with a non-permissive or unknown license, it opens a Linear issue assigned to the legal-review team with the model, license.
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.