DATA OPS
Warehouse Table Freshness SLA Watchdog with Upstream Lag Attribution
Compares each Snowflake table's actual landing time against its expected SLA, and when a table is late.
How it runs
The automated pipeline, trigger to output.
- TriggerEvery 15 minutes on schedule
- ActionQuery Snowflake table landing timestampsSnowflake
- LogicKeep tables past their SLA window
- ActionTrace lineage to slowest upstream sourceSnowflake
- OutputPage table owner with lag attributionPagerDuty
What it does
This watchdog checks whether your critical Snowflake tables landed on time. For every table that breached its freshness SLA, it traces back through the table's lineage to identify the slowest upstream dependency, then pages the owner with the lag attributed to a specific source rather than a vague "data is late" alert.
When to use it
Run it on a tight cadence (every 15-30 minutes) for the tables that feed executive dashboards, billing, or downstream exports. It is built for teams who get paged about stale data but waste the first 20 minutes figuring out which job in the chain actually stalled.
How it works
- 1A schedule fires on the watchdog interval.
- 2It queries Snowflake's table metadata for `last_altered` / max load timestamps on each monitored table.
- 3A logic step compares actual landing time to the expected SLA window and keeps only the breaches.
- 4For each breach, it queries the dependency graph in Snowflake to find the latest-landing upstream source.
- 5It opens a PagerDuty incident routed to the table owner, with the offending upstream source named in the summary.
Set it up
What you configure once, before turning it on.
- 1Connect SnowflakeWarehouses, queries, shares.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 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
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.