DATA OPS
BigQuery Slot/Cost Telemetry to Axiom with PagerDuty Escalation
Streams BigQuery job cost and slot-ms telemetry into Axiom on a tight interval and pages on-call via PagerDuty when hourly spend breaches a rolling budget guardrail.
How it runs
The automated pipeline, trigger to output.
- TriggerEvery 5 minutes interval
- ActionFetch BigQuery jobs since last checkpointBigQuery
- ActionForward cost + slot telemetry to AxiomAxiom
- LogicProject rolling hourly spend vs budget guardrail
- OutputTrigger PagerDuty incident on breachPagerDuty
What it does
Ships fine-grained BigQuery job telemetry — bytes billed, slot-ms, query labels, and reservation — into Axiom every few minutes so you get live dashboards and retention beyond INFORMATION_SCHEMA's window. On top of that stream it enforces a rolling hourly budget: if projected spend blows through the guardrail, it pages the data on-call through PagerDuty before the damage compounds across a full day.
When to use it
Use this when you run reservations or flat-rate slots and a single runaway query or backfill can torch your budget within hours. Daily digests are too slow; this is the real-time tripwire.
How it works
- 1An interval trigger fires every 5 minutes.
- 2BigQuery returns jobs completed since the last checkpoint with cost and slot fields.
- 3The events are forwarded into Axiom for dashboards and long-term retention.
- 4A logic step projects the rolling hourly spend and compares it to the budget guardrail.
- 5If breached, PagerDuty triggers an incident routed to the data on-call.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect AxiomLog streams, queries, dashboards.
- 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 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.