ENGINEERING
Hourly error-budget sweep freezes burning services
Every hour, queries Honeycomb SLO burn rates across all tracked services, freezes GitLab merges only on the services over budget, and posts a per-service status table to Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerHourly schedule
- ActionQuery Honeycomb burn rate per SLOHoneycomb
- LogicBranch each service: freeze, unfreeze, or skip
- ActionApply batch GitLab label changesGitLab
- OutputPost per-service status table to SlackSlack
What it does
Runs a scheduled sweep across every service that has an SLO defined in Honeycomb, evaluates each one's burn rate, and selectively freezes or unfreezes the matching GitLab project. Instead of one alert per service, you get one consolidated hourly status with the freeze state for each.
When to use it
Use it when you run many services and don't want a webhook storm — a single periodic source of truth that reconciles freeze state across the whole fleet. Good for platform teams owning a service-to-project map.
How it works
- 1An hourly schedule triggers the run.
- 2The workflow queries Honeycomb for the current burn rate of each configured SLO.
- 3For each service, it branches: over-threshold services get the GitLab `merge-freeze` label applied; recovered services have it removed; unchanged ones are skipped.
- 4It executes the GitLab label changes in batch.
- 5It posts a single Slack message with a per-service table showing burn rate, budget remaining, and current freeze state so the whole team sees the fleet at a glance.
Set it up
What you configure once, before turning it on.
- 1Connect HoneycombDistributed traces and queries.
- 2Connect GitLabRepos, MRs, pipelines, registry.
- 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.