Monitor usage with system tables

Preview

This feature is in Public Preview. There are currently no charges to use this feature. In the future, some of this usage might incur a charge.

This article explains the concept of system tables in Databricks and highlights resources you can use to get the most out of your system tables data.

What are system tables?

System tables are a Databricks-hosted analytical store of your account’s operational data found in the system catalog. System tables can be used for historical observability across your account.

Note

For documentation on system.information_schema, see Information schema.

Requirements

Which system tables are available?

Currently, Databricks hosts the following system tables:

Table

Description

Location

Supports streaming

Retention

Include global or regional data

Audit logs

Includes records for all audit events across your Databricks account. For a list of available audit events, see Audit log reference.

system.access.audit

Yes

365 days

Regional for workspace-level events. Global for account-level events.

Table lineage

Includes a record for each read or write event on a Unity Catalog table or path.

system.access.table_lineage

Yes

365 days

Regional

Column lineage

Includes a record for each read or write event on a Unity Catalog column (but does not include events that do not have a source).

system.access.column_lineage

Yes

365 days

Regional

Billable usage

Includes records for all billable usage across your account. Each usage record is an hourly aggregate of a resource’s billable usage.

system.billing.usage

Yes

365 days

Global

Pricing

A historical log of SKU pricing. A record gets added each time there is a change to a SKU price.

system.billing.list_prices

No

N/A

Global

Jobs

Tracks all jobs created in the account.

system.workflow.jobs

Yes

365 days

Regional

Job tasks

Tracks all job tasks that run in the account.

system.workflow.job_tasks

Yes

365 days

Regional

Job run timeline

Tracks the start and end times of job runs.

system.workflow.

job_run_timeline

Yes

365 days

Regional

Job task timeline

Tracks the start and end times and compute resources used for job run tasks.

system.workflow.

job_task_run_timeline

Yes

365 days

Regional

Marketplace funnel events

Includes consumer impression and funnel data for your listings.

system.marketplace.listing_

funnel_events

Yes

365 days

Regional

Marketplace listing access

Includes consumer info for completed request data or get data events on your listings.

system.marketplace.listing_

access_events

Yes

365 days

Regional

Note

You may see other system tables in your account besides the ones listed above. Those tables are in Private Preview currently and are empty by default. If you are interested in using any of these tables, please reach out to your Databricks account team.

Enable system table schemas

Since system tables are governed by Unity Catalog, you need to have at least one Unity Catalog-enabled workspace in your account to enable and access system tables. System tables include data from all workspaces in your account but they can only be accessed from a Unity Catalog-enabled workspace.

System tables are enabled at the schema level. If you enable a system schema, you enable all the tables within that schema. When new schemas are released, an account admin needs to manually enable the schema.

System tables must be enabled by an account admin. You can enable system tables using the SystemSchemas API.

Note

The billing schema is enabled by default. Other schemas must be enabled manually.

  • Use the List system schemas API to view which schemas are available and enabled in your account. The schemas will have one of the following states:

    • state: AVAILABLE: The system schema is available but has not yet been enabled.

    • state: EnableCompleted: You have enabled the system schema and it is visible in Catalog Explorer.

  • Use the Enable system schema API to add the schema to your system catalog.

  • Use the Disable system schema API to remove a schema from your system catalog.

Grant access to system tables

System table access is governed by Unity Catalog. By default, no users have access to system tables. To grant access, a metastore admin or other privileged user must grant USE and SELECT permissions on the system schemas. See Manage privileges in Unity Catalog.

System tables are read-only and cannot be modified.

Note

If your account was created after March 6, 2024, you might not have a metastore admin by default. For more information, see Set up and manage Unity Catalog.

Do system tables contain data for all workspaces in your account?

The audit log and lineage tables contain operational data for all workspaces in your account deployed within the same cloud region. The billing system table (system.billing.usage) contains data for all workspaces in your account, no matter what region they are deployed in.

Even though system tables can only be accessed through a Unity Catalog workspace, the tables also include operational data for non-Unity Catalog workspaces in your account.

Where are the system tables located?

The system tables in your account are located in a catalog called system, which is included in every Unity Catalog metastore. In the system catalog you’ll see schemas such as access and billing that contain the system tables.

Note

During the system tables Public Preview, Databricks will retain all your system tables data.

Considerations for streaming system tables

Access to system tables is supported by Delta Sharing. Be aware of the following considerations when streaming with Delta Sharing:

  • If you are using streaming with system tables, set the skipChangeCommit option to true. This ensures the streaming job is not disrupted from deletes in the system tables. See Ignore updates and deletes.

  • Trigger.AvailableNow is not supported with Delta Sharing streaming. It will be converted to Trigger.Once.

  • If you use a trigger in your streaming job and find the job isn’t catching up to the latest system table version, Databricks recommends increasing the scheduled frequency of the job.

Known issues

  • Currently no support for real-time monitoring. Data is updated throughout the day. If you don’t see a log for a recent event, check back later.