ENGINEERING
Weekly error-budget report with auto-filed Linear follow-ups
Each week this flow pulls burn rate and budget remaining for every tracked Honeycomb SLO, posts a ranked summary to Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule
- ActionQuery each tracked Honeycomb SLOHoneycomb
- LogicRank services + flag over-budget ones
- ActionOpen Linear issue per over-budget serviceLinear
- OutputPost ranked budget digest to SlackSlack
What it does
Gives the team a recurring read on error-budget health and turns the worst offenders into tracked work. Weekly, it gathers burn rate and remaining budget for each tracked Honeycomb SLO, ranks them, posts a digest to Slack, and files a Linear issue for every service that finished the week over its budget so reliability debt does not get forgotten.
When to use it
Use it to run a lightweight weekly reliability review without anyone assembling the numbers by hand, and to ensure over-budget services automatically get a ticket and an owner. Best for teams running multiple Honeycomb SLOs and managing work in Linear.
How it works
- 1A weekly schedule triggers the report.
- 2The flow queries each tracked Honeycomb SLO for burn rate and budget remaining.
- 3A logic step ranks services and flags any that ended over budget.
- 4Linear opens a follow-up issue for each over-budget service with the figures.
- 5Slack receives the ranked digest with links to the new Linear issues.
Set it up
What you configure once, before turning it on.
- 1Connect HoneycombDistributed traces and queries.
- 2Connect LinearIssues, projects, cycles, triage.
- 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
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…
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.
Scan for deprecated endpoints and email consumers a weekly sunset countdown
On a weekly schedule, scans the OpenAPI spec for endpoints marked deprecated with a sunset date, and emails each consuming team a countdown of how many days remain before removal.
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.
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.
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.