Connector docs — Databricks
Exactly what CostMon asks for to read Databricks
CostMon runs a read-only SQL statement against system.billing.usage joined to system.billing.list_prices via the Databricks SQL Statement Execution API.
What CostMon calls
The literal API surface, nothing more
- POST /api/2.0/sql/statements
- SELECT against system.billing.usage joined to system.billing.list_prices, grouped by usage date, SKU, and workspace.
- GET /api/2.0/sql/statements/{id}/result/chunks/{n}
- Paged result-chunk fetch for the same statement.
What you supply
Credential and config fields
tokenAccess token (PAT or OAuth)secretrequired
hostWorkspace URLrequired
warehouse_idSQL warehouse IDrequired
Minimum permission
Copy this, not a broader role
Scope of access
What Databricks access can't reach
- Notebooks, jobs, clusters, or any data outside the two system.billing tables
- Query history or content run by your own users
Worth knowing
- Dollar amounts are LIST-PRICE ESTIMATES from system.billing.list_prices, not your negotiated/invoiced price, and they exclude the underlying cloud infrastructure cost. Usage (DBUs) is exact; dollars are directional.
FAQ
Common questions about the Databricks connector
Are the dollar amounts my actual negotiated Databricks price?
No. They're list-price estimates from system.billing.list_prices, and they don't include the underlying cloud infrastructure cost. Usage in DBUs is exact; treat the dollar figure as directional.
Does the connector see my notebooks or job definitions?
No. It only ever queries the two system.billing tables listed above, and only needs SELECT on those plus warehouse access to run the query.
A rate you looked up will change again.
Provider pricing pages change without notice. CostMon tracks the bill that pays for it.