Automated Databricks Usage Cost Reviews
Every Monday, WebRun opens Databricks, reads the last seven days of compute usage across workspaces, clusters, and jobs, appends the consumption figures to Airtable so a trend builds, and writes a Notion note naming the biggest consumers, the fastest growers, and any cluster left running with nothing on it.
How do I review my Databricks compute usage every week?
WebRun reads the last seven days of Databricks compute usage every Monday across workspaces, clusters, and jobs. It appends the figures to Airtable so a trend builds with an owner on every line, then writes a Notion review naming the biggest consumers, the fastest growers, and any cluster that ran while idle.
- Runaway compute is named on Monday, not on the invoice
- Every consumption line carries an owning team
- Idle clusters get surfaced while the week is still young
Built for data platform teams · analytics engineers · FinOps · 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
databricks.comin a real browser with your saved login - no setup, no API keys. -
1
Databricks - read last week's usage
databricks.com
WebRun opens Databricks to read last week's usage. - Open Databricks and go to the usage view for the last seven days
- Capture consumption by workspace, by cluster, and by job for the period
- Note which clusters ran with little or no workload attached
- Compare each figure against the same period a week earlier
Done when Last week's consumption is captured per workspace, cluster, and job, with a week over week change.
-
2
Airtable - log consumption by cluster
airtable.com
WebRun opens Airtable to log consumption by cluster. - Open your platform cost base in Airtable
- Append one dated row per cluster and per job with its consumption for the week
- Link rows to the owning team so cost has a name attached to it
- Flag any line that has grown for three weeks in a row
Done when Airtable holds this week's consumption rows with owners and growth flags.
-
3
Notion - write the cost review
notion.so
WebRun opens Notion to write the cost review. - Open your data platform page in Notion and add a dated review entry
- List the top consumers of the week with their figures and their owning team
- Name the fastest growing lines and the clusters that ran while idle
- Suggest the obvious questions to ask, and leave any decision to shut something down to the team
Done when Notion holds a dated cost review ranking last week's Databricks consumption.
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
Will it terminate clusters or change job settings?
No. WebRun reads usage views in Databricks only. It never stops a cluster, edits a job, changes a schedule, or runs a notebook. Shutting anything down stays a human decision.
Does it read the data in my tables?
No. It reads consumption and job metadata such as names, owners, and runtimes. It never queries a table, opens a notebook's contents, or exports any dataset.
How does it know which team owns a cluster?
It reads the creator and any tags on the cluster or job in Databricks, then matches them to the owner mapping in your Airtable base, which you can correct at any time.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.