DATA OPS
BigQuery Slot-Hog Detection and Owner Linear Tickets
Detects scheduled queries that exceed a slot-ms or scan-bytes budget, then opens a Linear ticket assigned to the query owner with the offending SQL and a cost breakdown attached.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule every few hours
- ActionAggregate slot-ms and bytes scanned per scheduled queryBigQuery
- LogicFilter to over-budget queries and dedupe open tickets
- ActionCreate Linear issue assigned to query ownerLinear
- OutputPost new-ticket summary to SlackSlack
What it does
Scans recent BigQuery job history for scheduled queries whose consumed slot-ms or bytes-scanned blow past a configured budget, identifies the owner from the query's `owner` label, and files a Linear issue assigned directly to that person. The ticket carries the query name, the SQL text, slot-ms consumed, and estimated cost so the owner can fix or schedule it without a back-and-forth.
When to use it
Use this when a few heavy scheduled queries dominate your reservation and you want accountability tracked as work, not just a Slack ping that scrolls away. It converts a slot-utilization spike into an assigned, trackable task.
How it works
- 1A schedule runs every few hours.
- 2Query `INFORMATION_SCHEMA.JOBS` for scheduled-query jobs and aggregate slot-ms and bytes scanned per query.
- 3Filter to queries above the slot or scan budget; deduplicate against tickets already open.
- 4For each new offender, resolve the owner from its label.
- 5Create a Linear issue assigned to the owner with SQL, slot-ms, and cost in the body.
- 6Post a short summary of new tickets to Slack.
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
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.