legacy Public Preview
Billable usage log delivery
Billable usage log delivery is legacy, replaced by System tables (legacy since 2025).
Billable usage log delivery System tables
Account-level delivery of billable usage logs as CSV files to your own S3 bucket - one file per workspace, refreshed daily through an Account API log delivery configuration - so DBU usage could be analysed outside the account console.
- A log delivery configuration is immortal: the docs say you cannot delete one, only disable it, and re-enabling it fails if it would now break the two-per-level limit.
- "Daily delivery" meant rewriting the same file: every day Databricks overwrote the current month's CSV for each workspace instead of appending a fresh one.
- Its memory has a hard floor - the API will not start delivery for any month before March 2019, because billable usage logs are simply not available before then.
Limitations: Still in Public Preview and does not record usage for all products - Databricks points to system tables for complete usage logs. An account gets at most two enabled account-level configurations and two per specific workspace, and a configuration can be disabled but never deleted.
Open in REbricked →- Category
- Data governance
- Also known as
- Billable usage logs, Billable usage logs (legacy), BILLABLE_USAGE log delivery, Usage logs to S3
- Verified
- 2026-09-11
Sources
- Official Official Databricks / Microsoft docs
- Official Databricks release notes: billable usage logs delivered to your own S3 bucket (Public Preview, June 30, 2020)
- Official Databricks release notes: Account API GA, billable usage delivery remains in Public Preview (September 2020)
- Official Databricks REST API reference: create a log delivery configuration (log_type BILLABLE_USAGE)