Service Integrations
Databricks
Configure Pelanor to ingest cost and usage data from Databricks system tables through Unity Catalog.
Prerequisites
Requirement | Purpose |
---|---|
Unity Catalog enabled | Exposes Databricks system tables for querying. |
Metastore admin role | Needed to enable system schemas. |
Databricks CLI | Used to enable schemas and list workspace metadata. |
Step-by-Step Setup
1
Enable Unity Catalog
Ensure Unity Catalog is active for the target workspace. Follow Databricks’ official documentation if it is not already enabled.
2
Enable System Schemas
3
(Optional) Create a Warehouse
Pelanor can query any existing warehouse, but a small serverless warehouse with auto-stop is recommended for cost efficiency.
4
Create a Service Principal
- Open Account Console → Service principals.
- Click Add Service principal, assign a clear name, then Generate Secret.
- Save the Client ID and Secret—you will enter these in Pelanor.
5
Grant Workspace & Warehouse Access
- In Account Console → Workspaces, add the Service Principal to the workspace with User permission.
- Inside the workspace, open the warehouse → Permissions → grant Can Use.
- Confirm the principal has the Databricks SQL access entitlement.
6
Grant System-Table Privileges
Run the following SQL (replace the placeholder with the Service Principal ID):
Additional Notes
- Multiple Workspaces – Granting access in one workspace lets Pelanor collect data for all spend in the Databricks account—no per-workspace connection needed.
- Pricing Source – The current adaptor uses Databricks list prices. Custom price books are not yet supported.