Improved query audit for Databricks Unity Catalog
Immuta’s Unity Catalog improved query audit is now enabled for all accounts. The Databricks Unity Catalog audit ingestion query now uses the system.query.history table from Databricks. This foundational change significantly improves the match rate between Unity Catalog query audit records and Immuta-managed data sources, delivering more accurate and valuable insights.
What's New
There's now a better linkage between queries run in Unity Catalog and their associated data sources in the Immuta audit dashboards and reports, providing a clearer, more reliable picture of data access usage within Unity Catalog.
In addition to better linkage, the rowsProduced parameter is now also getting populated for Unity Catalog query audits.
- The following parameters are no longer populated, as they are not available in the system.query.history table: userAgent, requestId, clientIp.
🗓 The release of this feature followed Immuta’s behavior change release process. For details about each phase, see the Behavior change release process page.
- Opt-in period: 10/1 - 10/31
- Opt-out period: 11/1 - 11/30
- Enabled for all accounts: 12/1
Note: If you were using Immuta's Databricks UC audit feature without the required privileges for this change, Immuta disabled the audit ingest feature.
🔎 Learn more about Databricks Unity Catalog Query Audit Logs in the documentation
