DATA OPS
BigQuery Scheduled-Query Cost Regression Sentinel
Every morning, checks each BigQuery scheduled query's bytes-billed against its 14-day baseline and posts a ranked Slack digest of the queries whose cost regressed.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily 7am schedule
- ActionQuery JOBS for per-query bytes billed + 14d baselineBigQuery
- LogicCompute regression %, keep queries over threshold
- ActionAttribute each flagged query to its last editorBigQuery
- OutputPost ranked cost-regression digest to SlackSlack
What it does
Runs a daily sweep over `INFORMATION_SCHEMA.JOBS` to compute yesterday's bytes-billed for every scheduled query, compares each against its trailing 14-day median, and flags the ones that jumped past a regression threshold. The result is one tidy Slack digest ranked by dollars of waste, with the responsible owner @-mentioned, so cost creep gets caught the same day it starts instead of at month-end invoice.
When to use it
Use this when your team relies on dozens of scheduled queries and your BigQuery bill drifts up quietly. It's the early-warning layer that turns a surprise invoice into a Monday-morning fix.
How it works
- 1A 7am schedule fires the sentinel.
- 2BigQuery query rolls up per-query bytes-billed for yesterday plus the 14-day median baseline.
- 3A logic step computes the percent regression and keeps only queries above the threshold (e.g. +40% and >100 GB).
- 4An owner-attribution step joins each flagged query to its last-modifier from the transfer-config metadata.
- 5Slack posts the ranked digest with estimated cost delta and owner mentions.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Data Ops workflows
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 orphan model detector with Linear cleanup tickets
Scans your dbt manifest for models that no other model, exposure, or BI tool consumes.
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.
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.
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…
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.