DATA OPS
BigQuery Cost-to-Commit Blame Correlator
When a scheduled query's cost regresses, it diffs the query SQL against its prior version in your dbt/SQL Git repo and posts the responsible commit, author, and SQL diff to Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule
- ActionFind queries regressed vs 7-day baselineBigQuery
- LogicSelect worst regressor, map to source file
- ActionFetch file commit history + diffGitHub
- LogicExtract author, SHA, SQL hunks
- OutputPost blamed commit + diff to SlackSlack
What it does
Links a BigQuery slot-hour spike to the exact Git commit that edited the offending query's SQL, surfacing the author and the line-level diff that caused the regression.
When to use it
When scheduled queries are version-controlled (dbt models, raw `.sql` files) and you want cost regressions tied directly to the code change that introduced them, so the fix goes straight to the person who shipped it.
How it works
- 1A scheduled trigger runs each morning.
- 2A BigQuery query finds scheduled queries whose slot-hours rose sharply versus their 7-day baseline.
- 3A logic step picks the single worst regressor and maps it to its source file path.
- 4A GitHub action fetches the recent commit history for that file and the diff between the last two changes.
- 5A logic step extracts the author, commit SHA, and SQL hunks.
- 6A Slack message posts the spike size, the blamed commit, author, and the SQL diff for review.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 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.