DEVOPS
Edge Canary: Post-Deploy Bake Report to GitHub and Slack
Once a Cloudflare canary reaches the end of its bake window, pulls the full Honeycomb error-budget and latency comparison, posts a pass/fail summary as a GitHub deployment status.
How it runs
The automated pipeline, trigger to output.
- TriggerBake-window-end schedule tick
- ActionQuery Honeycomb error rate and p95 by versionHoneycomb
- LogicDerive pass/fail verdict from deltas
- ActionWrite GitHub deployment status on release commitGitHub
- OutputSend bake report to release Slack channelSlack
What it does
Closes out a canary bake with a verdict. When the bake timer ends, it gathers the canary-versus-stable error rate and p95 latency from Honeycomb, renders a concise pass/fail report, writes it back as a GitHub deployment status on the release commit, and announces the result so the team knows whether the version is cleared to fully promote.
When to use it
Use when canary promotion is a human decision but you want the data assembled and stamped on the PR automatically — no one has to hand-build the comparison or hunt for the right Honeycomb query after every deploy.
How it works
- 1A schedule fires at the end of the configured bake window for an active deploy.
- 2The workflow queries Honeycomb for canary and stable error rate plus p95 latency, keyed by version.
- 3A logic branch derives a pass/fail verdict from the deltas against your thresholds.
- 4It posts a GitHub deployment status (success or failure) with the metrics on the release commit.
- 5It sends a formatted bake report to the release Slack channel with a Honeycomb link.
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
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.