Databricks · Cost monitoring
Track the workspaces and products driving Databricks DBUs
Bring account-wide DBU usage into one cost review with your cloud and AI providers. Compare workspaces and SKUs, identify the change, and make the pricing assumptions visible before sharing a forecast.
Built for Data-platform administrators and FinOps teams.
14-day trial · No credit card required · Plans from $79/month
Illustrative connection workflow. No account is connected by viewing this page.
The problem
What brings Databricks teams here?
DBU usage can grow across workspaces and product categories before the next budget review. A list-rate estimate helps explain the direction, but it must not be mistaken for a negotiated Databricks invoice or job-level attribution.
The solution and buyer value
How StackSpend helps with Databricks
- 01
Find the workspace or product category that moved
Review available DBU usage by workspace and SKU/product category to choose where a deeper investigation should start.
- 02
Keep estimated value explicit
Read the calculated cost alongside its list-rate basis and configured discount, so the team understands why it may differ from the invoice.
- 03
Bring data workloads into the shared cost review
Compare Databricks trends with connected cloud and AI sources, then use Databricks for the job- or resource-level detail required to act.
Before you connect
Check Databricks coverage and access
- Source and coverage
- Daily billing-system usage by workspace, SKU, cloud and product, multiplied by effective USD list prices. An optional uniform discount is a connection-level assumption.
- Required access
- OAuth M2M service principal with billing-table read grants and SQL warehouse access, or a supported personal access token. See the exact setup requirements.
- History and freshness
- Initial sync requests up to 90 days where available. Databricks reporting delays and scheduled sync apply; new workspaces may take longer to appear.
Limits to check
- List-rate estimates can differ from negotiated invoices
- No job, cluster, SQL-warehouse resource or user attribution from this connector
- Underlying AWS, Azure or GCP infrastructure charges require their own connection
Evaluate the connection
From setup to a useful Databricks review
Match DBU quantity, then explicitly document the rate/discount basis.
Check system-table access- OAuth M2M service principal with billing-table read grants and SQL warehouse access, or a supported personal access token. See the exact setup requirements.
- Choose Databricks in StackSpend and follow the setup guide to test the connection.
- After a successful sync, compare the returned date range, currency and cost basis with the provider. Record gaps before relying on a total.
Databricks questions before you connect
Do these dollars match our Databricks invoice?
They are usage multiplied by effective list prices, with an optional uniform discount assumption. They can differ from negotiated invoice amounts. Compare usage quantities first and state your rate assumption when sharing totals.
Do I need to connect every workspace?
The billing system tables can provide account-wide usage through one eligible workspace connection. Verify the returned workspace coverage and required Unity Catalog permissions.
Does the DBU total include my cloud infrastructure bill?
Do not assume that. Cloud infrastructure may be billed separately. Keep Databricks usage-based estimates and separately connected cloud charges clearly identified to avoid omissions or double counting.