DATA OPS
BigQuery Table Freshness SLA Breach Monitor
Each morning it checks the last-modified timestamp of a set of tables that scheduled queries should have refreshed overnight.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily after refresh window
- ActionQuery table last-modified timesBigQuery
- LogicFlag tables past freshness SLA
- OutputPost SLA breach report to SlackSlack
- ActionPage owner for critical tablesPagerDuty
What it does
It enforces a freshness SLA on tables that scheduled queries are supposed to refresh. Instead of trusting that a job ran, it reads each target table's actual last-modified time and compares it against the maximum allowed staleness, catching jobs that silently no-opped, got disabled, or fell behind.
When to use it
Use it when downstream consumers depend on tables being current by a deadline (for example, a finance mart that must be refreshed before the 8am exec review). It catches the failure mode where a query reports success but writes nothing, which run-status checks miss.
How it works
- 1A daily schedule fires after the overnight refresh window closes.
- 2A BigQuery action queries `INFORMATION_SCHEMA` for the last modification time of each monitored table.
- 3A logic step computes staleness per table and selects any that exceed their configured SLA threshold.
- 4If any table is stale, a Slack output posts a breach report listing each table, its age, and its owner.
- 5For tables marked critical, a PagerDuty action raises a low-urgency incident so the owner is notified directly.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 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.