DATA OPS
Critical Source Freshness Breach to PagerDuty
Every 15 minutes checks tier-1 BigQuery source tables; if a revenue- or billing-critical source has stopped loading, it pages the on-call data engineer through PagerDuty…
How it runs
The automated pipeline, trigger to output.
- Trigger15-minute critical-source check
- ActionQuery tier-1 source load timesBigQuery
- LogicBranch on SLA breach
- ActionBuild downstream impact lineageBigQuery
- ActionRaise PagerDuty incidentPagerDuty
- OutputPost incident + impact to SlackSlack
What it does
Monitors only the source tables you tag as tier-1 (billing, revenue, identity) for ingestion gaps. When one of these critical sources stops receiving rows past its tight freshness threshold, it raises a PagerDuty incident so someone is paged, rather than filing a ticket that waits until morning.
When to use it
Use it for the small set of sources where a stalled pipeline means broken invoices or wrong revenue numbers, and a delayed response is unacceptable. This is the loud, page-someone counterpart to the routine Linear-ticket sentinel.
How it works
- 1A 15-minute schedule triggers the check.
- 2It queries `INFORMATION_SCHEMA` for the max load timestamp of every source tagged tier-1 in the dbt manifest.
- 3A branch separates sources within SLA from those breached.
- 4For breached sources, it builds the downstream-impact lineage list of dependent models.
- 5It triggers a PagerDuty incident with severity scaled to how many downstream models are affected.
- 6It posts the incident link plus impacted-model list to the incident 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
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.