DATA OPS
Hourly dbt Source Freshness SLA Monitor
Runs dbt source freshness checks on a schedule and pages the data on-call only when a source breaches its SLA threshold, so stale upstream data is caught before models build on it.
How it runs
The automated pipeline, trigger to output.
- TriggerHourly schedule fires
- ActionQuery Snowflake source load timestampsSnowflake
- LogicClassify sources: healthy / warn / error vs SLA
- ActionOpen PagerDuty incident for error breachesPagerDuty
- OutputPost warning breaches to SlackSlack
What it does
Proactively guards against stale source tables. On a fixed cadence it evaluates the max-loaded-at timestamp of each registered dbt source against its warn and error thresholds, and escalates the breaches instead of waiting for a model to fail downstream.
When to use it
Use it when your warehouse depends on third-party loaders (Fivetran, custom syncs) that can silently stop. Catching a frozen source at the source level is far cheaper than debugging wrong numbers in a dashboard hours later.
How it works
- 1A schedule fires every hour.
- 2The flow queries Snowflake for the latest load timestamp of each source table and computes lag against its SLA.
- 3A logic step splits sources into healthy, warning, and error tiers.
- 4Error-tier breaches open a PagerDuty incident routed to the data on-call.
- 5Warning-tier breaches post to Slack so the team can watch without being paged.
Set it up
What you configure once, before turning it on.
- 1Connect SnowflakeWarehouses, queries, shares.
- 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
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.