DATA OPS
Postgres Source-Schema Sentinel with PagerDuty Escalation on Breaking Drift
Polls a source Postgres database for column drops and type narrowing, classifies each change as breaking or additive.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule fires every few minutes
- ActionRead source schema from Postgres information_schemaPostgres
- LogicDiff against baseline and classify breaking vs additive
- ActionOpen PagerDuty incident for breaking driftPagerDuty
- OutputLog additive changes to SlackSlack
What it does
This sentinel watches a source Postgres database and distinguishes severity. Adding a nullable column is additive and harmless; dropping a column or narrowing a type (e.g. `text` to `varchar(20)`) is breaking. It pages on-call only for breaking drift so dependent ingestion jobs can be halted before they corrupt downstream tables, and records additive changes without waking anyone.
When to use it
Use it when you ingest from an application database you don't control and need genuine on-call signal — not noise — the moment a column your ETL depends on disappears or changes shape.
How it works
- 1A schedule fires every few minutes.
- 2Query `information_schema.columns` on the source Postgres for the watched tables.
- 3Compare to the stored baseline; classify each delta as additive or breaking.
- 4Branch on severity: breaking drift takes the escalation path, additive drift takes the log path.
- 5Breaking -> open a PagerDuty incident with the table, column, and old/new type.
- 6Additive -> post a low-priority note to Slack and update the baseline.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 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.