DATA OPS

Daily warehouse top-spender digest to Slack

Every morning, ranks yesterday's most expensive BigQuery query authors by bytes billed and posts a leaderboard to Slack so the data team sees who is driving spend before the bill…

CategoryData Ops
Enginesim
Difficultybeginner
Triggerschedule
Steps4
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily 8am schedule
  • ActionAggregate yesterday's job cost per author from INFORMATION_SCHEMA.JOBSGoogle BigQueryBigQuery
  • LogicRank authors by cost, keep top 10 with priciest query
  • OutputPost leaderboard digest to Slack channelSlack

What it does

Queries BigQuery's `INFORMATION_SCHEMA.JOBS` for the prior day, aggregates total bytes billed and estimated dollar cost per user, and posts a ranked top-10 leaderboard to a Slack channel. Each row shows the author, job count, total cost, and the single most expensive query.

When to use it

Run this when warehouse spend is creeping up and nobody knows who owns it. A daily public leaderboard creates gentle social pressure and gives the data platform team an at-a-glance view of cost concentration without opening the billing console.

How it works

  1. 1A scheduled trigger fires each morning at 8am.
  2. 2A BigQuery action runs an aggregation over `INFORMATION_SCHEMA.JOBS` for the previous calendar day, grouping by `user_email` and computing `SUM(total_bytes_billed)` converted to dollars at the on-demand rate.
  3. 3A logic step sorts authors by cost descending and keeps the top 10, attaching each author's single priciest query text.
  4. 4A Slack action posts the formatted leaderboard with totals and per-author breakdown to the data-ops channel.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect BigQueryDatasets, queries, schemas.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.