DATA OPS
BigQuery Row-Count Anomaly Detector to PagerDuty
Compares each day's ingested row count for key BigQuery tables against a rolling baseline and pages on-call via PagerDuty when volume spikes or collapses beyond the expected band.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily load-complete event
- ActionFetch today's count + rolling baselineBigQuery
- LogicDetect volume outside expected band
- LogicSkip tables within tolerance
- OutputOpen PagerDuty incident per anomalyPagerDuty
What it does
After the daily load completes, this workflow measures how many rows landed in each monitored BigQuery table and compares that to a rolling 14-day median and standard deviation. A load that is far above or below the normal band, including an empty load, is treated as a volume anomaly. Confirmed anomalies open a PagerDuty incident with the table name, today's count, and the expected range so the on-call engineer can triage a broken pipeline before it corrupts reporting.
When to use it
Use this when partial loads, duplicate ingests, or upstream API outages quietly change data volume without throwing an error. Row-count drift is often the earliest signal that a pipeline is silently wrong.
How it works
- 1A completed-load event triggers the run.
- 2A BigQuery query returns today's row count and the rolling baseline per table.
- 3A logic step flags tables whose count falls outside the median plus or minus the configured deviation band.
- 4A branch suppresses pages for tables within tolerance.
- 5A PagerDuty incident is opened for each anomalous table with the deviation details attached.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 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.