DATA OPS
BigQuery Cost Spike to Owner-Assigned Linear Ticket
When a single scheduled query's daily cost more than doubles its baseline, opens a Linear issue pre-assigned to the query's owner with the diagnostic query text and cost math…
How it runs
The automated pipeline, trigger to output.
- TriggerDaily 6am schedule
- ActionPull per-query cost vs 30-day baselineBigQuery
- LogicKeep queries that 2x'd and crossed dollar floor
- ActionResolve owner from transfer-config metadataBigQuery
- ActionCreate assigned Linear issue with SQL + cost mathLinear
- OutputPost issue link to SlackSlack
What it does
Watches for hard cost spikes on individual BigQuery scheduled queries and, instead of just alerting, files an actionable Linear issue. The issue is assigned to the engineer who owns the query, titled with the query name and cost delta, and pre-filled with the offending SQL, the bytes-billed trend, and a checklist for remediation (partition filter, clustering, materialization). It turns a cost anomaly into tracked, owned work.
When to use it
Use this when alerts alone get ignored. Routing a spike straight into your issue tracker as assigned work creates accountability and a paper trail your data platform team can review in standup.
How it works
- 1A 6am schedule triggers the check.
- 2BigQuery pulls each scheduled query's yesterday cost versus its 30-day baseline.
- 3A logic gate keeps only queries that at least doubled and crossed a dollar floor.
- 4For each survivor, an owner lookup resolves the assignee from transfer-config metadata.
- 5Linear creates an assigned issue with SQL text, cost math, and a remediation checklist.
- 6Slack drops a thread link so the owner sees it immediately.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect LinearIssues, projects, cycles, triage.
- 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
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 orphan model detector with Linear cleanup tickets
Scans your dbt manifest for models that no other model, exposure, or BI tool consumes.
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.
Backfill Missing Owner Labels on BigQuery Scheduled Queries
Finds scheduled queries with no owner label, infers the likely owner from creator metadata and target-table lineage, proposes a label.
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.
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…
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.