DATA OPS
Live DDL-change interceptor to PagerDuty
Receives a webhook the instant a DDL change runs against a watched warehouse table and pages on-call via PagerDuty when the change touches a column that feeds a production model.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook receives DDL-change eventHTTP webhook
- LogicClassify operation as risky or benign
- LogicMatch table against production-critical list
- OutputPage on-call via PagerDuty for risky critical changesPagerDuty
- OutputLog benign changes to SlackSlack
What it does
Turns warehouse DDL events into real-time alerts. When an `ALTER TABLE` or `DROP COLUMN` lands on a table you've marked as production-critical, it decides whether the change is dangerous and escalates to PagerDuty only when it is — no noise for benign additions.
When to use it
You run a warehouse where schema changes can happen any time of day, and a dropped or retyped column on a hot table is a genuine incident. Polling once a day is too slow; you need to know within seconds.
How it works
- 1An HTTP webhook receives the DDL event payload (table, operation, affected columns).
- 2A logic step classifies the operation: adds are informational, drops and type changes are risky.
- 3A second logic branch checks the affected table against your list of production-critical tables.
- 4If a risky change hit a critical table, trigger a PagerDuty incident with the column and operation details.
- 5Otherwise post a low-priority note to Slack for the record.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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.