DATA OPS
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…
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule several times daily
- ActionQuery month-to-date bytes billed grouped by teamBigQuery
- LogicCompare to budget, select newly-breaching teams
- ActionTrigger PagerDuty incident on team servicePagerDuty
- OutputAppend breach snapshot to Postgres ledgerPostgres
What it does
Rolls up month-to-date scheduled-query cost by `team` label, compares each team against its configured monthly budget, and when a team exceeds it, triggers a PagerDuty incident routed to that team's escalation policy. It also appends the breach snapshot to a Postgres ledger so finance has an auditable record of when and why a budget was blown.
When to use it
Use this when teams own their BigQuery budgets and a runaway scheduled query can burn the monthly allocation in a day. Pages the right on-call the moment a budget is crossed instead of surfacing it on the next invoice.
How it works
- 1A schedule runs several times a day.
- 2Query `INFORMATION_SCHEMA.JOBS` for month-to-date bytes billed and group by `team` label.
- 3Compare each team's spend to its budget; select teams newly over budget since the last run.
- 4Trigger a PagerDuty incident on each breaching team's service.
- 5Append the breach snapshot (team, spend, budget, top queries) to the Postgres ledger.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 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.
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.
Backfill Missing Owner Labels on BigQuery Scheduled Queries
Finds scheduled queries with no owner label, infers the likely owner from creator metadata and target-table lineage, proposes a label.
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.