Databricks
Pull Databricks billable usage (DBUs) and workspace inventory from the account console to break down the Azure Databricks bill by workspace, cluster, SKU, and owner.
Questions you can answer 21
Each one is a saved query that ships with ConfigView, reading your Databricks data on your own server. Ask it in plain English, SQL, Slack or the API.
- How has Databricks usage changed day by day?
- Show the daily DBU trend for Databricks
- When did our Databricks spend spike?
- Who is generating the most Databricks cost?
- Break down Databricks DBUs by cluster owner
- Which users' clusters are burning the most DBUs?
- Which Databricks workspace is driving the Azure bill?
- Show DBUs per Databricks workspace
- How much Databricks compute does each workspace use?
- Break down Databricks DBUs by billing SKU
- Is jobs compute or all-purpose compute costing us more in Databricks?
- Which Databricks SKU is the biggest cost driver?
- Which Databricks clusters use the most DBUs?
- Find oversized or runaway Databricks clusters
- Show the top 10 Databricks clusters by consumption
- Which Databricks clusters have no cost-allocation tags?
- Find Databricks spend we can't charge back to a team
- Show untagged Databricks usage
- What Databricks workspaces do we have?
- List every Databricks workspace with its region, tier and subscription
- Which Azure subscription does each Databricks workspace bill to?
No Databricks questions match that yet. Try a shorter word.
What ConfigView collects from Databricks 2
-
Workspaces
Account workspace inventory — name, Azure region, pricing tier, status, and the subscription / resource group each workspace bills into.
-
Billable Usage
Per-day DBU and machine-hour consumption for every workspace, cluster, and billing SKU — the line-item detail behind the Azure Databricks invoice.