DATA OPS
Escalate critical BigQuery SLA breaches to PagerDuty
Fires when a freshness-breach event arrives by webhook, and for tier-1 tables that are past a hard deadline it opens or updates a PagerDuty incident with the table, lateness…
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook receives freshness-breach eventHTTP webhook
- ActionResolve downstream view blast radiusBigQuery
- LogicCheck table tier and hard-deadline threshold
- ActionOpen or update deduped PagerDuty incidentPagerDuty
- OutputLink incident in on-call Slack channelSlack
What it does
It receives breach events from the watchdog and decides which ones deserve a page. Low-tier tables are logged and ignored; tier-1 tables that blow a hard SLA threshold open a PagerDuty incident enriched with the affected downstream views and minutes-late. A dedup key keyed on the table ensures repeated breach pings update the existing incident instead of paging again.
When to use it
Use it when a stale critical dataset is an actual on-call event, not just a Slack note. Keeps the pager quiet for non-critical lateness while guaranteeing tier-1 data outages wake someone.
How it works
- 1A webhook trigger receives a freshness-breach event from the watchdog.
- 2A BigQuery action resolves the downstream view blast radius for the breached table.
- 3A logic step checks the table's tier and whether it crossed the hard deadline.
- 4For qualifying breaches, a PagerDuty action opens or updates an incident using a per-table dedup key.
- 5A Slack message links the incident in the on-call channel as the final notification.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect BigQueryDatasets, queries, schemas.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Data Ops workflows
Snowflake column type-drift sentinel with Linear fix ticket
Snapshots the data types of every column in your tracked Snowflake schemas on a schedule, diffs against the last snapshot.
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 dropped/renamed column sentinel with PagerDuty incident
Detects when a column is dropped or renamed in your governed BigQuery datasets and, because that breaks downstream queries hard, pages the on-call via PagerDuty and posts…
PR-time Snowflake schema contract check on dbt model changes
When a pull request changes a dbt model, it compares the model's declared output columns against the live Snowflake table it will replace and blocks the merge with a GitHub check…
Agent-triaged warehouse drift with impact analysis and runbook update
On a webhook from your warehouse audit log, an agent investigates the changed column, traces which downstream models and dashboards depend on it.
Cross-warehouse replication schema mismatch reconciler
Compares the column shape of mirrored tables between BigQuery and Snowflake and, when a replicated table has drifted out of sync between the two, opens an Asana task for the data…
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.