DEVOPS
Guard p95 latency SLO during a flag rollout and freeze on burn
Monitors p95 latency for the flagged cohort against your SLO and, when the error budget burn rate is too steep, freezes the rollout in GitHub and asks the release owner…
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule fires every minute during rollout
- ActionQuery Honeycomb for p95 latency and SLO burn rateHoneycomb
- LogicBranch: burn rate above fast-burn threshold?
- ActionFreeze flag at current rollout percentage via GitHubGitHub
- OutputSend Slack approve-rollback decision to release ownerSlack
What it does
Protects a latency SLO while a flag ramps. Instead of a hard auto-kill, it freezes the rollout at its current percentage and hands a clear yes/no rollback decision to the release owner.
When to use it
Use for performance-sensitive changes where a small latency regression is tolerable but a fast error-budget burn is not. Good when you want a human in the loop for the final rollback call but want the ramp paused instantly.
How it works
- 1A schedule runs every minute during the rollout.
- 2A Honeycomb query computes p95 latency and the SLO burn rate for the flag-on cohort.
- 3A logic branch checks the burn rate against your fast-burn threshold.
- 4If the budget is burning too fast, a GitHub action pins the flag at its current rollout percentage so it cannot advance.
- 5A Slack interactive message goes to the release owner with the latency chart link and Approve-rollback / Hold buttons.
- 6The approved choice writes the final flag state back through GitHub.
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.