← All updates Databricks Update One-Pager Navy version
databricks Platform · Updated Sep 23, 2026

Lakebase observability telemetry in system tables (Beta)

Lakebase captures its Postgres observability telemetry into the system.lakebase system tables, with no configuration to create and no destination to choose.

What it does

Lakebase captures its Postgres observability telemetry into the system.lakebase system tables, with no configuration to create and no destination to choose. Query plans, session history, wait events, schema change history, database and compute health, and Postgres logs land there, and records are retained for 7 days. Account admins and metastore admins can read the tables and manage access to them, and a user with access queries the telemetry the way they would any Unity Catalog table.

Why it matters

Access The system.lakebase tables are governed by Unity Catalog.

Architecture
Databricks Platform → Platform
In short

Lakebase captures its Postgres observability telemetry into the system.lakebase system tables, with no configuration to create and no destination to choose. Query plans, session history, wait events, schema change history, database and compute health, and…

Read the full documentation ↗
Key takeaway
Lakebase captures its Postgres observability telemetry into the system.lakebase system tables, with no configuration to create and no destination to choose.
2026-09-23-lakebase-observability-telemetry-in-system-tables-beta Generated by the Databricks Updates Agent · browse all updates