DEVOPS
Weekly Honeycomb SLO Burn-Down Snapshot to BigQuery and Slack Digest
Each week snapshots every Honeycomb SLO's burn rate and remaining budget into a BigQuery table for trend history, then posts a ranked digest of the worst-trending SLOs to Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires
- ActionRead all SLO metrics from HoneycombHoneycomb
- ActionAppend weekly snapshot rows to BigQueryBigQuery
- ActionQuery week-over-week budget deltasBigQuery
- OutputPost ranked burn-down digest to SlackSlack
What it does
Collects a weekly point-in-time snapshot of all Honeycomb SLOs — burn rate, budget consumed, and budget remaining — and appends it to a BigQuery history table. It then queries the table for week-over-week deltas and posts a Slack digest ranking the SLOs whose budget is eroding fastest. The outcome is a durable burn-down history you can chart, plus a weekly heads-up on the worst-trending reliability targets.
When to use it
Use this when Honeycomb's native retention is too short for the quarterly trend reporting you need, or when leadership wants a regular reliability digest backed by your own warehouse data.
How it works
- 1A weekly schedule trigger fires.
- 2The flow reads current budget and burn metrics for every SLO from Honeycomb.
- 3It appends one row per SLO to a BigQuery snapshot table with the run timestamp.
- 4A BigQuery query computes the week-over-week budget delta and ranks the steepest declines.
- 5A Slack digest posts the top decliners with their burn multiple and remaining budget to the reliability channel.
Set it up
What you configure once, before turning it on.
- 1Connect HoneycombDistributed traces and queries.
- 2Connect BigQueryDatasets, queries, schemas.
- 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.