DATA OPS
dbt Source Freshness Breach to PagerDuty Escalation
Runs dbt source freshness checks on a schedule, and when a critical source exceeds its staleness threshold.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule every 30 minutes
- ActionRun dbt source freshnessShell
- ActionConfirm max loaded-at per sourceSnowflake
- LogicSplit critical (error) vs advisory (warn)
- ActionOpen PagerDuty incident on critical breachPagerDuty
- OutputPost breaching tables and incident link to SlackSlack
What it does
This sentinel executes `dbt source freshness` against your Snowflake warehouse on a fixed cadence, parses the resulting `sources.json`, and isolates any source whose loaded-at lag has crossed its `error_after` threshold. Critical breaches page on-call through PagerDuty; the same breach is mirrored to Slack with the exact table names and lag durations.
When to use it
Use it when stale source data silently poisons everything downstream — a partner feed that stopped landing at 2am shouldn't be discovered at noon by a confused analyst. Best for teams with SLAs on a handful of revenue- or compliance-critical sources.
How it works
- 1A schedule fires every 30 minutes during business-critical windows.
- 2A shell step runs `dbt source freshness` and writes `sources.json`.
- 3Snowflake is queried to confirm the max loaded-at timestamp per flagged source.
- 4A logic branch separates `error` (critical) from `warn` (advisory) states.
- 5On critical, PagerDuty opens an incident tagged with the source name and lag.
- 6The final Slack message lists each breaching table, its lag, and the incident link.
Set it up
What you configure once, before turning it on.
- 1Connect SnowflakeWarehouses, queries, shares.
- 2Connect ShellRun sandboxed commands inside the workspace.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.