DATA OPS
Publish a monthly BigQuery attribution-coverage report
At month-end, aggregates BigQuery spend into attributed vs still-unattributed, breaks attributed cost down by team.
How it runs
The automated pipeline, trigger to output.
- TriggerMonth-end schedule after final daily attribution
- ActionAggregate monthly spend into attributed vs unattributedBigQuery
- LogicCompute coverage %, MoM delta, per-team breakdown
- ActionRender coverage report to a Notion pageNotion
- OutputPost Slack summary linking the reportSlack
What it does
Produces a monthly scorecard of how much BigQuery spend is now attributed to a team versus still unowned, with a per-team breakdown and the trend versus the prior month.
When to use it
Run it at month close to show progress on the attribution program and to give finance a defensible team-by-team cost split. It answers 'what percent of our warehouse bill can we actually assign to an owner?'
How it works
- 1A month-end schedule starts the run once the final daily attribution lands.
- 2Query total BigQuery spend for the month split into attributed and unattributed buckets.
- 3Compute coverage percentage and compare it to the prior month stored in a metrics table.
- 4Break attributed spend down by team and rank the largest spenders and the biggest unattributed principals.
- 5Render the figures into a Notion report page with a coverage headline and the breakdown tables.
- 6Post a Slack summary linking the report with coverage percent and month-over-month change.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect NotionPages, databases, comments.
- 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.