DEVOPS
Daily Worker canary rollout digest from Axiom
Once a day, summarizes every Worker version that was canaried, promoted, or rolled back.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule: daily
- ActionRead 24h rollout ledger from PostgresPostgres
- ActionEnrich events with Axiom error ratesAxiom
- LogicCompose digest; flag flapping versions
- ActionArchive raw rows as CSV to R2Cloudflare R2
- OutputPost digest to DiscordDiscord
What it does
Gives the team a single daily readout of Worker delivery health. It reads the rollout ledger, enriches each promotion and rollback with the error-rate numbers Axiom recorded at decision time, and produces a digest that says which versions advanced, which were reverted, and why. A CSV of the raw rows is archived for the record.
When to use it
Use it for weekly review prep, incident retros, and giving non-on-call stakeholders visibility into how aggressive or stable your rollouts have been — without anyone digging through logs or dashboards.
How it works
- 1A schedule fires once daily.
- 2The rollout ledger for the last 24 hours is read from Postgres.
- 3For each version event, Axiom is queried for the error rate captured around that decision.
- 4A logic step composes the digest, grouping promotions vs. rollbacks and flagging any version that flapped.
- 5The raw rows are written as a CSV to R2 for archival.
- 6The formatted digest is posted to Discord with a link to the archived CSV.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect AxiomLog streams, queries, dashboards.
- 3Connect Cloudflare R2Object storage, S3-compatible.
- 4Connect DiscordCommunity channels + voice + bots.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.