DATA OPS
Continuous prod schema baseline with PagerDuty alert on unexpected drift
Stores a known-good production schema baseline and re-checks production against it on a tight schedule.
How it runs
The automated pipeline, trigger to output.
- TriggerFrequent schedule
- ActionRead live production schemaPostgres
- ActionLoad stored schema baselinePostgres
- LogicDiff vs baseline; classify expected vs out-of-band
- OutputPage on-call via PagerDuty on unexpected driftPagerDuty
What it does
This workflow treats your production schema as state that should only change through deploys. It keeps a stored baseline snapshot and, on a frequent schedule, compares live production against it. Any difference that appears outside a recognized deploy window is treated as an out-of-band change and pages on-call through PagerDuty.
When to use it
Use it to catch unauthorized or accidental schema edits made directly against production — a contractor running an `ALTER TABLE` in psql, an emergency hotfix nobody captured as a migration. These are exactly the changes that break the next real migration.
How it works
- 1A frequent schedule triggers the check.
- 2Read the live production schema catalog from Postgres.
- 3Load the stored baseline snapshot for comparison.
- 4Diff live against baseline.
- 5Branch: if a deploy window is active or the diff is empty, refresh the baseline and exit; otherwise treat it as unexpected drift.
- 6Page on-call via PagerDuty with the offending objects and the exact DDL change.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 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.