DATA OPS
BigQuery Source Freshness Breach to PagerDuty On-Call Escalation
Watches BigQuery source-load freshness against tiered SLAs and, when a critical source breaches, opens a PagerDuty incident routed to the data on-call while logging a warning…
How it runs
The automated pipeline, trigger to output.
- TriggerHourly schedule
- ActionRead latest load time per source from BigQueryBigQuery
- LogicClassify lateness: none / soft / hard by tier
- ActionOpen PagerDuty incident for hard critical breachesPagerDuty
- OutputPost freshness summary + soft warnings to SlackSlack
What it does
This workflow tracks freshness for BigQuery source tables and applies tiered SLAs: soft breaches get a logged warning, while hard breaches on business-critical sources page the on-call engineer through PagerDuty. It turns silent late loads into an alert with the right urgency instead of a dashboard nobody is watching at 2am.
When to use it
Use it when some data sources are mission-critical (revenue, billing, fraud) and a late load there warrants waking someone, while others only need a heads-up. Ideal for teams already running PagerDuty for on-call.
How it works
- 1A schedule runs hourly.
- 2Query BigQuery INFORMATION_SCHEMA for the latest partition/load time per tracked source.
- 3A logic step classifies each lateness as none, soft, or hard against the source's tier and SLA.
- 4For hard breaches on critical sources, open a PagerDuty incident with the source, lateness, and downstream impact.
- 5Post a consolidated freshness summary to Slack covering soft warnings and resolved sources.
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
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.