DATA OPS
BigQuery Contract Breach Pager for Breaking Drift
Watches BigQuery for breaking schema changes against the dbt contract and pages on-call via PagerDuty only when a column is dropped or retyped in a way that will fail the next…
How it runs
The automated pipeline, trigger to output.
- TriggerFrequent schedule during ingest hours
- ActionRead live BigQuery table schemasBigQuery
- LogicClassify diff: breaking (drop/retype) vs. non-breaking
- ActionTrigger PagerDuty incident on breaking driftPagerDuty
- OutputPost full diff and incident link to SlackSlack
What it does
This sentinel separates breaking drift from harmless drift. It diffs BigQuery table schemas against your dbt contracts and classifies each change: an added nullable column is informational, but a dropped column or a narrowing type change is breaking. Only breaking changes page the on-call engineer through PagerDuty, with a Slack message carrying the full diff so they can triage without logging into the warehouse.
When to use it
Reach for this when broken dbt builds are an incident-grade event, not a morning-ticket event, and you already run PagerDuty for on-call. It keeps the pager quiet for cosmetic schema additions while guaranteeing a human is woken for the changes that actually halt the pipeline.
How it works
- 1A frequent schedule polls BigQuery during active ingest hours.
- 2Read live table schemas via the BigQuery API.
- 3Load the matching dbt contract for each contracted model.
- 4Classify the diff into breaking vs. non-breaking changes.
- 5If a breaking change exists, trigger a PagerDuty incident scoped to the table owner.
- 6Post the full diff and incident link to the data Slack channel for shared context.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 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.