DATA OPS
dbt Source Freshness Watchdog: Page On-Call When Sources Stall
Polls source-table load lag in Snowflake against dbt source freshness thresholds and, when an upstream feed stops arriving, escalates to PagerDuty so the pipeline owner is paged…
How it runs
The automated pipeline, trigger to output.
- TriggerEvery 15 minutes
- ActionQuery latest row timestamp per source tableSnowflake
- LogicClassify each source healthy / warn / error
- ActionPost warn-level heads-up to SlackSlack
- OutputOpen PagerDuty incident for stalled sourcesPagerDuty
What it does
Monitors the freshness of raw source tables, the ones dbt sources are built on, rather than the marts. It compares the most recent row timestamp per source against the warn and error windows you set. A warn-level lag posts to Slack; an error-level lag (the feed has genuinely stopped) triggers a PagerDuty incident routed to the pipeline's on-call.
When to use it
Use when stale dashboards are usually caused by an upstream feed that quietly stopped, not by dbt itself. Catching the source at the warn stage gives you a head start before the staleness propagates into every dependent model.
How it works
- 1A schedule runs every 15 minutes.
- 2A Snowflake query returns the latest row timestamp for each monitored source table.
- 3A logic step classifies each source as healthy, warn, or error against its thresholds.
- 4Warn-level sources are summarized into a single Slack heads-up message.
- 5Error-level sources open a PagerDuty incident with the source name and observed lag.
Set it up
What you configure once, before turning it on.
- 1Connect SnowflakeWarehouses, queries, shares.
- 2Connect SlackChannels, DMs, threads, mentions.
- 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
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.