DATA OPS
Escalate repeat BigQuery slot offenders to PagerDuty after nudges are ignored
Tracks daily slot-contention nudges per author and, when the same author tops the contention ranking three days running, escalates to the on-call data platform owner…
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule after ranking computed
- ActionQuery JOBS for today's top slot consumersBigQuery
- ActionUpdate per-author flag streaks in state tablePostgres
- LogicBranch when streak reaches three days
- ActionTrigger PagerDuty incident for on-call ownerPagerDuty
- OutputPost escalation heads-up to SlackSlack
What it does
It closes the loop on friendly nudges. The workflow keeps a running count of how many consecutive days each author has been flagged as a top slot consumer, and when someone ignores the gentle Slack reminders and stays at the top for three straight days, it escalates to the on-call platform owner so a human intervenes.
When to use it
Use it when self-service nudges aren't enough and a small number of authors keep saturating the reservation. It ensures persistent contention becomes a tracked operational item rather than a recurring annoyance the team learns to ignore.
How it works
- 1A daily schedule fires after the contention ranking is computed.
- 2Query `INFORMATION_SCHEMA.JOBS` to identify today's top slot consumers.
- 3Read each author's recent flag history from a state table in Postgres and update streak counts.
- 4Branch: if an author's consecutive-flag streak reaches three, escalate; otherwise just persist the updated state.
- 5Trigger a PagerDuty incident for the on-call owner with the author, three-day slot history, and worst queries.
- 6Post a heads-up in the escalation Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 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.