DATA OPS

BigQuery Scheduled-Query Daily Health Digest

Once each morning it compiles every scheduled query's last-run status, duration, and bytes processed into a single digest table and posts a ranked summary so the data team has…

CategoryData Ops
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily before standup
  • ActionQuery 24h job historyGoogle BigQueryBigQuery
  • LogicAggregate health metrics per query
  • ActionWrite digest to history tableGoogle BigQueryBigQuery
  • OutputPost daily digest to SlackSlack

What it does

It produces a single daily rollup of the health of all scheduled queries in a project: pass/fail counts, the slowest jobs, the most expensive jobs, and any that didn't run at all. It replaces clicking through the BigQuery console with one readable report.

When to use it

Use it for a calm, scheduled morning review rather than real-time paging. Good for a data team that wants a standing health snapshot and a record they can scroll back through, without noise for every transient blip.

How it works

  1. 1A daily schedule fires before standup.
  2. 2A BigQuery action queries the last 24 hours of `INFORMATION_SCHEMA.JOBS` joined against the list of active transfer configs.
  3. 3A logic step aggregates per query: final state, duration, bytes billed, and whether an expected run is missing.
  4. 4A BigQuery action writes the rollup into a dated history table for trend tracking.
  5. 5A Slack output posts the digest with success/fail tallies and the top slowest and costliest queries linked to the console.

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.