DATA OPS
Postgres breaking-change sentinel to PagerDuty
Polls a production Postgres table's schema and pages on-call via PagerDuty only for breaking changes — dropped or retyped columns — while logging additive changes quietly.
How it runs
The automated pipeline, trigger to output.
- Trigger15-minute schedule polls the table
- ActionRead column shape from Postgres information_schemaPostgres
- LogicClassify deltas as additive vs. breaking
- ActionPage on-call via PagerDuty for breaking changesPagerDuty
- ActionUpdate baseline schemaPostgres
What it does
Separates harmless schema growth from genuinely dangerous changes. New nullable columns are logged and ignored; dropped columns or narrowed types page the on-call engineer through PagerDuty so a pipeline break never goes unnoticed overnight.
When to use it
Use it on the few Postgres tables whose contract truly matters — billing, identity, the core fact table — where a removed or retyped column means immediate downstream failure and is worth waking someone for.
How it works
- 1A schedule polls the table on a tight interval (every 15 minutes).
- 2The flow reads column names, types, and nullability from `information_schema.columns` in Postgres.
- 3A logic step classifies each delta: additive (new column) versus breaking (drop or type change).
- 4If only additive changes exist, it records them to a log table and exits without alerting.
- 5If any breaking change is found, it triggers a PagerDuty incident with severity based on the column's criticality and attaches the diff.
- 6The baseline schema is updated for the next poll.
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.