ENGINEERING
Weekly BigQuery top-offenders report to Confluence with trend deltas
Every week, ranks the queries that consumed the most BigQuery bytes and the ones whose cost grew fastest week-over-week, then publishes a Confluence page with the leaderboard.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule
- ActionAggregate this week vs last week by query hashBigQuery
- LogicRank top consumers and fastest climbers
- ActionGather plan summaries for top offendersBigQuery
- OutputPublish Confluence top-offenders reportConfluence
What it does
This produces a recurring, shareable digest rather than per-incident tickets. It rolls up a week of BigQuery usage, ranks the heaviest queries and the steepest week-over-week climbers, and writes a Confluence page leadership and the data platform team can review together. Each entry carries a plan summary so the report doubles as a tuning backlog.
When to use it
Use for weekly platform reviews where you want a single living document of where BigQuery spend goes and which queries are trending the wrong way. Pairs well with the real-time and daily hunters for after-the-fact accountability.
How it works
- 1A weekly schedule kicks off the rollup.
- 2BigQuery job history is aggregated by query hash for this week and last week.
- 3A logic step ranks top consumers and computes week-over-week cost deltas, flagging the fastest climbers.
- 4Plan summaries are gathered for the top offenders.
- 5A Confluence page is published with the leaderboard, deltas, and plan notes as the final output.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect ConfluenceSpaces, pages, blueprints.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Engineering workflows
Gate breaking API PRs behind downstream consumer acknowledgement
When a PR introduces a breaking contract change, comments the impact summary back on the PR, applies a blocking label.
Publish a versioned API changelog to Confluence on each release tag
On a new semver release tag, gathers the contract changes since the last release and writes a clean.
Agent reviews model-license fit and suggests compliant swaps on the PR
When a PR adds a Hugging Face model, an agent reads the model card and license, judges fit against your commercial-use policy.
Upgrade Impact Router to Module Code Owners
Maps a dependency-bump PR's affected modules to their CODEOWNERS, then DMs each owner on Slack with only the changelog slice that touches code they own.
Re-Voice IVR Prompts on Phone-Tree Config Merge
When a phone-tree config change merges in GitHub, regenerates the ElevenLabs audio for any prompt whose script changed in the diff and opens a follow-up PR adding the new audio…
Upstream Release to Notion Upgrade Brief
When a watched package publishes a new release, fetches the release notes, maps them to the internal modules that depend on it.
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.