DATA OPS
Axiom Ingest Budget Burn-Rate Escalator
Hourly tracks month-to-date Axiom ingest against the monthly budget, and when the projected overage burn-rate is too high it identifies the top offending services and pages…
How it runs
The automated pipeline, trigger to output.
- TriggerHourly schedule
- ActionQuery Axiom month-to-date ingestAxiom
- LogicProject month-end and compare to budget
- ActionQuery Axiom top contributing servicesAxiom
- ActionTrigger PagerDuty overage incidentPagerDuty
- OutputPost burn-rate summary to SlackSlack
What it does
Guards the monthly Axiom budget by watching burn rate, not just totals. Every hour it projects end-of-month ingest from month-to-date usage, and if you're trending over budget it ranks the services responsible and escalates so someone can throttle logging before the overage lands.
When to use it
Use it when finance has a hard Axiom ingest budget and a mid-month overrun means real money. The burn-rate projection catches a slow leak days before a simple total-threshold alarm would.
How it works
- 1An hourly schedule starts the check.
- 2It queries Axiom for month-to-date ingest bytes across all datasets.
- 3A logic step projects month-end usage from the elapsed fraction of the month and compares it to the budget.
- 4If projected overage exceeds the threshold, it queries Axiom for the services contributing the most month-to-date volume.
- 5It triggers a PagerDuty incident sized to the projected overage and attaches the top-offender breakdown.
- 6It posts a Slack summary with the burn-rate chart values and which services to trim first.
Set it up
What you configure once, before turning it on.
- 1Connect AxiomLog streams, queries, dashboards.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 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 Data Ops workflows
Weekly BigQuery Cost Trend Sheet and Exec Digest
Compiles week-over-week BigQuery scheduled-query cost by owner and dataset into a Google Sheet with trend columns.
Daily BigQuery Scheduled-Query Cost Attribution to Owners
Each morning, totals the prior day's on-demand bytes-billed per scheduled query, maps each query to its owner from a label, and posts a per-owner cost leaderboard to Slack.
BigQuery Per-Team Budget Breach Alert to PagerDuty
Tracks month-to-date BigQuery scheduled-query spend per team and, when a team crosses its monthly budget, pages the team's on-call in PagerDuty and snapshots the spend breakdown…
dbt source freshness watcher with severity-routed alerts
Checks Snowflake loaded-at timestamps against each dbt source's freshness SLA, then routes warnings to Slack and hard breaches to a PagerDuty incident so stale data never…
dbt orphan model detector with Linear cleanup tickets
Scans your dbt manifest for models that no other model, exposure, or BI tool consumes.
Raw Sensor Telemetry Archive to BigQuery
Captures every incoming building sensor reading via webhook, normalizes the payload into a consistent schema.
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.