DATA OPS
Page On-Call When Critical Tables Drift
Watches a curated set of revenue-critical tables and, when BigQuery and Snowflake schemas diverge in a breaking way, opens a PagerDuty incident with the exact column-level diff…
How it runs
The automated pipeline, trigger to output.
- TriggerFrequent critical-table schedule
- ActionRead BigQuery critical schemasBigQuery
- ActionRead Snowflake critical schemasSnowflake
- LogicClassify drift as breaking or benign
- LogicBranch: escalate only breaking drift
- OutputOpen PagerDuty incident with diffPagerDuty
What it does
For a small list of business-critical tables, this workflow continuously checks for breaking schema divergence between BigQuery and Snowflake. When it finds a difference that would break downstream consumers (a dropped column, an incompatible type change), it escalates by opening a PagerDuty incident containing the precise diff and the affected table.
When to use it
Use it for the handful of tables where drift means revenue reporting or a customer-facing metric silently goes wrong. A daily Slack digest is too slow for these; you want a page the moment they diverge.
How it works
- 1A frequent schedule trigger runs the critical-table check.
- 2It reads the BigQuery schema for the critical table set.
- 3It reads the Snowflake schema for the same tables.
- 4A logic step classifies any diff as breaking or benign.
- 5A branch routes only breaking drift forward.
- 6It opens a PagerDuty incident with the column-level detail attached.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect SnowflakeWarehouses, queries, shares.
- 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
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.