DEVOPS
Auto-lift the deploy freeze when error budget recovers
On a schedule, re-checks the Honeycomb SLO burn rate and, once it has stayed under the safe threshold long enough, removes the GitHub deploy-freeze and announces that shipping is…
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule: re-check burn rate during freeze
- ActionQuery current SLO burn rate from HoneycombHoneycomb
- LogicRequire sustained recovery below threshold
- ActionRemove deploy-freeze label + clear blocking checkGitHub
- OutputPost all-clear with freeze duration to SlackSlack
What it does
This is the release valve for an error-budget freeze. It periodically asks Honeycomb whether the burn rate has settled, and when the SLO has been healthy for a sustained window it automatically unlocks the repo and tells the team they can deploy again — so freezes don't linger after recovery.
When to use it
Pair it with any burn-rate freeze workflow. Use it when you want freezes to be self-resolving rather than relying on someone to remember to flip the repo back on.
How it works
- 1A schedule trigger runs every few minutes during the freeze window.
- 2An action queries the current burn rate and remaining budget for the SLO from Honeycomb.
- 3A logic step requires the burn rate to be below threshold for a configured sustained period (debounce) before acting, avoiding flapping.
- 4If recovered, an action removes the `deploy-freeze` label and clears the blocking status check on the GitHub repo.
- 5The output posts an all-clear to Slack with the recovered burn rate and how long the freeze lasted.
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 DevOps workflows
Slack-approved pause for idle Hugging Face Spaces
On a daily scan it finds idle paid Spaces and posts an interactive Slack approval; on approve it pauses the Space and logs the decision to a GitHub issue audit trail.
Block costly Hugging Face Space hardware upgrades in PR review
When a pull request changes a Space's hardware config, it estimates the new monthly cost and posts a GitHub PR comment that flags upgrades crossing a budget ceiling.
Hugging Face Spaces idle-runtime sweep with auto-pause
On a schedule, scans all Hugging Face Spaces for ones running idle past a threshold, pauses them to stop billing, and posts a Slack summary with the estimated monthly savings.
Open a Zoom war-room from a Datadog multi-alert storm
When a Datadog monitor crosses a critical threshold, this workflow dedupes against active incidents, and only for a genuinely new outage it creates a Zoom bridge.
Auto-spin a Zoom war-room when PagerDuty hits SEV-1
When a PagerDuty incident escalates to a critical severity, this workflow creates a dedicated Zoom meeting and posts the bridge link to the incident's Slack channel so responders…
Spin up a war-room on demand from a Slack slash command
When an engineer runs a Slack command, this workflow creates a Zoom bridge, opens a tracking Sentry-linked incident, files a Linear issue for follow-up.
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.