Automated Starburst Weekly Query Cost Scorecard
Every Monday morning, WebRun opens Starburst, reads last week's query volume, data scanned, and compute usage broken down by team or catalog, posts a summarized cost scorecard to Slack ranking the heaviest users, and sends the full breakdown to Telegram, so platform leads can see who is driving cost before it becomes a budget problem.
How do I get a weekly query cost scorecard from Starburst?
WebRun reads last week's query volume, data scanned, and compute usage by team in Starburst every Monday, posts a ranked cost scorecard to Slack, and sends the full breakdown to Telegram. Platform leads see who is driving cost before it becomes a budget surprise, without pulling usage reports out of Starburst by hand.
- Platform leads see cost drivers weekly instead of at the monthly bill
- Heavy usage jumps get flagged before they become a budget surprise
- A full usage breakdown is always available in Telegram for reference
Built for Data platform teams · Platform engineering leads · FinOps teams · Data engineering managers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
galaxy.starburst.ioin a real browser with your saved login - no setup, no API keys. -
1
Starburst - read last week's query usage
- Open Starburst and read last week's query volume and data scanned by team
- Calculate compute usage for each team or catalog
- Rank teams from heaviest to lightest usage
Done when Every active team or catalog has last week's usage figures.
-
2
Slack - post the cost scorecard
slack.com
WebRun opens Slack to post the cost scorecard. - Post a summarized scorecard ranking teams by usage
- Call out any team whose usage jumped sharply from the prior week
- Keep the post short and scannable
Done when The platform channel has this week's cost scorecard.
-
3
Telegram - send the full breakdown
telegram.org
WebRun opens Telegram to send the full breakdown. - Send the full usage breakdown by team and catalog
- Include the query count and data scanned for each
- Keep it as a reference message platform leads can search back to
Done when The full breakdown has been sent to Telegram.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does WebRun limit or throttle anyone's queries?
No. It only reports usage. Setting limits on a team's compute or catalog access stays a decision for your platform lead.
Where does the detailed breakdown live?
In Telegram, sent as a full reference message alongside the shorter Slack scorecard, so anyone can look up the exact numbers behind the summary.
What if a team's usage jump was expected, like a big migration?
It still gets flagged in the scorecard since the automation only reports the numbers. Context on why usage jumped stays with the team.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.