DATA OPS
Tiered dbt Freshness Escalation to PagerDuty
Escalates BigQuery model freshness breaches by severity tier — paging PagerDuty for revenue-critical models past a hard SLA while routing minor lateness to Slack only.
How it runs
The automated pipeline, trigger to output.
- TriggerEvery 5 minutes (schedule)
- ActionRead freshness age, tier, and SLA per modelBigQuery
- LogicSplit into tier-1 hard breaches vs. minor lateness
- ActionOpen/update PagerDuty incident for tier-1 breachesPagerDuty
- OutputPost low-noise summary of minor lateness to SlackSlack
What it does
Applies tiered urgency to freshness breaches. Tier-1 models (revenue, billing) that blow past a hard SLA trigger a real PagerDuty incident with on-call paging; lower-tier models or minor lateness get a quieter Slack heads-up. This stops alert fatigue while guaranteeing the truly critical tables wake someone up.
When to use it
Use this when you have a clear severity hierarchy across your models and need genuine paging (not just a chat message) for the data products that money or compliance depend on.
How it works
- 1A schedule fires every 5 minutes.
- 2BigQuery returns freshness ages and each model's configured tier and SLA.
- 3A logic step splits breaches into tier-1-hard-breach versus everything-else.
- 4Tier-1 hard breaches open or update a PagerDuty incident with the model, age, and runbook link.
- 5All other breaches post a low-noise summary to the data-ops Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 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.