DEVOPS
Axiom Daily Budget Breach: Slack Triage Thread with Deploy Suspects
Fires when Axiom's projected daily ingest cost crosses your budget ceiling, then posts a Slack triage thread that lists the candidate deploys and top datasets so on-call can…
How it runs
The automated pipeline, trigger to output.
- TriggerAxiom budget-breach webhook arrivesAxiom
- LogicDe-dupe so only one live thread per day
- ActionList today's Vercel prod deploys as suspectsVercel
- ActionPull top 3 Axiom datasets by ingest delta + costAxiom
- OutputPost Slack triage thread tagging on-call with next stepsSlack
What it does
Turns a raw Axiom budget breach into a ready-to-action Slack triage thread. Instead of a cryptic billing alert, your on-call sees which deploys landed today and which datasets are eating the budget, with interactive next steps.
When to use it
Use it when you have a hard daily logging budget and want humans in the loop for the call to roll back versus mute. Best for teams where muting a noisy logger is a judgment call, not something to automate blindly.
How it works
- 1An incoming Axiom monitor webhook fires when projected daily ingest cost crosses the budget ceiling.
- 2A logic step de-dupes against today's earlier alerts so the channel only gets one live thread per day.
- 3It queries Vercel for all production deploys since midnight and builds a suspect list ordered by recency.
- 4It pulls the top three Axiom datasets by ingest delta with per-dataset projected cost.
- 5It posts a Slack thread tagging the on-call group, summarizing the breach, suspects, and offending datasets, with suggested mute and rollback actions.
Set it up
What you configure once, before turning it on.
- 1Connect AxiomLog streams, queries, dashboards.
- 2Connect VercelDeploys, runtime logs, analytics.
- 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.