ENGINEERING
Slack Burn-Rate Alarm with Freeze-Merges Toggle
On a schedule, checks every tracked service's Honeycomb SLO burn rate and, when any service crosses fast-burn, posts a Slack alert and flips a merge-freeze flag the PR gate reads…
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled fleet burn-rate sweep
- ActionFetch burn rates for all tracked SLOs from HoneycombHoneycomb
- LogicFlag services over fast-burn threshold
- ActionPost Slack alert with per-service burn mathSlack
- OutputWrite merge-freeze flag to PostgresPostgres
What it does
Runs a fleet-wide burn-rate sweep on a timer rather than per-PR. It pulls the current burn rate for every service with a Honeycomb SLO, and when one crosses your fast-burn line it sends a Slack alert naming the service, the burn multiplier, and budget remaining. It then sets a shared merge-freeze flag in Postgres so the per-PR gate can refuse merges to that service until budget recovers.
When to use it
Use it when you want proactive, org-wide protection instead of reacting only when someone opens a PR. Good for teams running many services where a single hot SLO should pause all merges to it automatically.
How it works
- 1A schedule fires the sweep at your chosen interval.
- 2The flow fetches burn rates for all tracked SLOs from Honeycomb.
- 3A logic step flags any service over the fast-burn threshold.
- 4It posts a Slack alert with the burn math for each flagged service.
- 5It writes the merge-freeze flag to Postgres for downstream gates to enforce.
Set it up
What you configure once, before turning it on.
- 1Connect HoneycombDistributed traces and queries.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 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.