DATA OPS
BigQuery Cost Regression Auto-Incident
When a scheduled query's daily cost exceeds a hard dollar threshold, it opens a PagerDuty incident and a tracking issue in Linear with the attributed query and projected monthly…
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule
- ActionCompute per-query cost in dollarsBigQuery
- LogicFlag queries over dollar threshold + project overage
- ActionTrigger PagerDuty incidentPagerDuty
- OutputFile Linear tracking issueLinear
What it does
Escalates severe BigQuery cost regressions into real incidents: it converts daily slot-hours to dollars, and when one query crosses a hard spend threshold it pages on-call and files a tracking ticket with the projected monthly impact.
When to use it
For production warehouses where a runaway scheduled query can cost thousands before anyone notices. Use the dollar threshold to page only on genuinely expensive regressions, not noise.
How it works
- 1A scheduled trigger runs every morning.
- 2A BigQuery query computes per-scheduled-query slot-hours and converts to estimated cost using your on-demand or flat-rate pricing.
- 3A logic step flags any query whose daily cost rose above the configured dollar threshold and projects the monthly overage if sustained.
- 4If a query crosses the line, a PagerDuty action triggers an incident routed to the data on-call.
- 5A Linear action files a tracking issue with the query name, job ID, cost delta, and projection.
- 6If nothing crosses, the run ends without paging.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Connect LinearIssues, projects, cycles, triage.
- 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.