DEVOPS
Honeycomb SLO Burn-Rate Forecast to Scheduled Capacity Review
Reads each Honeycomb SLO's burn rate on a schedule, forecasts when the error budget will be exhausted.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires
- ActionFetch SLO budget and burn rate from HoneycombHoneycomb
- LogicForecast days-to-exhaustion per SLO
- LogicKeep SLOs projected to breach within horizon
- ActionCreate capacity review item on Mondaymonday.com
- OutputPost scheduled reviews summary to SlackSlack
What it does
Pulls live burn-rate and error-budget data for every Honeycomb SLO, projects the exhaustion date from the current trend, and pre-emptively schedules a capacity review for any SLO forecast to run out of budget before the next planning cycle. The outcome is that owners get a dated review item created before the SLO actually breaches, not after.
When to use it
Run this when you manage several reliability SLOs and want to act on burn-rate trends instead of waiting for alerts. It suits platform and SRE teams who plan capacity in sprints and want the forecast to drive the calendar automatically.
How it works
- 1A scheduled trigger fires every morning.
- 2The flow queries the Honeycomb SLO API for each SLO's current budget remaining and short-window burn rate.
- 3A forecast step linearly projects the days-to-exhaustion from the current burn rate.
- 4A logic branch keeps only SLOs projected to exhaust inside the planning horizon (for example 14 days).
- 5For each surviving SLO it creates a Monday item on the Capacity Reviews board with the owner, projected breach date, and current burn multiple.
- 6A Slack summary posts the day's newly scheduled reviews to the reliability channel.
Set it up
What you configure once, before turning it on.
- 1Connect HoneycombDistributed traces and queries.
- 2Connect monday.comVisual work management for teams.
- 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
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.
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…
Page on-call when a Hugging Face Space build is stuck or errored
Polls Hugging Face Space runtime status on a schedule and opens a PagerDuty incident when a Space sits in a build or error state past a deadline, with a Slack heads-up.
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.
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.
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.