MLflow trace storage in Unity Catalog is now generally available
docs.databricks.com databricks.com
This is what was read here when it was published. databricks.com no longer carries it in what it publishes now.
Listen to this summary
MLflow trace storage in Unity Catalog tables is now generally available. Databricks recommends storing traces in Unity Catalog for new and production workloads: storage is unlimited, traces are stored in OpenTelemetry (OTel) format, access is governed through Unity Catalog schema and table permissions, and you can query traces with SQL, Genie, AI/BI dashboards, and any Spark-based tool. To view traces, point an MLflow experiment at a Unity Catalog trace location. For supported regions, see Features with limited regional availability.
See Store OpenTelemetry traces in Unity Catalog and Observe and find issues.
More ways to use this
Open on another device
Scan to open this page. Your saved notes and account access are not included.