DATA OPS
Cross-Warehouse Replication Drift Detector
Compares table schemas between a Snowflake source and its BigQuery replica on a schedule, and pages on-call via PagerDuty when the two warehouses fall out of sync.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled comparison run
- ActionRead source contract from SnowflakeSnowflake
- ActionRead replica contract from BigQueryBigQuery
- LogicAlign columns and classify divergence severity
- OutputPage on-call via PagerDuty on high-severity driftPagerDuty
What it does
When the same logical table is replicated from Snowflake into BigQuery, the two copies can quietly diverge — a column added upstream that never propagated, or a type that mapped incorrectly. This workflow reads both schemas, aligns them by column, and reports every mismatch as a single drift report. If the divergence is severe, it pages on-call.
When to use it
Use it when you run a Snowflake-to-BigQuery replication and need confidence the replica's structure still matches the source. It catches silent replication gaps before analysts query a stale or malformed mirror.
How it works
- 1A scheduled run starts the comparison.
- 2Read the source table contract from Snowflake.
- 3Read the replica table contract from BigQuery.
- 4Align columns and classify each difference by severity.
- 5If a high-severity divergence is found, trigger a PagerDuty incident; otherwise log the clean run.
Set it up
What you configure once, before turning it on.
- 1Connect SnowflakeWarehouses, queries, shares.
- 2Connect BigQueryDatasets, queries, schemas.
- 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.