DEVOPS
Worker canary gate on Honeycomb latency SLO breach
When Honeycomb fires a P95-latency SLO-burn alert tied to a canary Worker version, this halts the rollout, freezes the traffic split.
How it runs
The automated pipeline, trigger to output.
- TriggerHoneycomb SLO burn-rate alert webhookHoneycomb
- LogicConfirm fast-burn and match active rollout
- ActionFreeze Cloudflare traffic splitCloudflare
- ActionFetch slow-trace exemplars from HoneycombHoneycomb
- OutputPage on-call via PagerDuty with tracesPagerDuty
What it does
Treats a canary Worker rollout as a latency risk, not just an error-rate risk. It listens for Honeycomb SLO burn-rate alerts scoped to the canary version and, on a fast-burn alert, immediately freezes the Cloudflare traffic split so the bad version stops gaining share, then escalates to PagerDuty with the slowest trace exemplars attached.
When to use it
Use it when your Worker's failure mode is slow rather than broken — timeouts, cold-start regressions, or a degraded upstream that still returns 200s. Error-rate gates miss these; a latency SLO gate catches them.
How it works
- 1A Honeycomb SLO burn-rate alert webhook fires referencing the canary version.
- 2A logic step confirms the alert is fast-burn and maps it to the active rollout.
- 3Cloudflare freezes the traffic split at its current percentage so the canary cannot grow.
- 4Honeycomb is queried for the top slow-trace exemplars in the burn window.
- 5PagerDuty is paged with the SLO context and trace links for the on-call engineer.
Set it up
What you configure once, before turning it on.
- 1Connect HoneycombDistributed traces and queries.
- 2Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 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.