Databricks MLflow becomes a supported OTel export destination for the Claude platform
Understand this story
Databricks says its MLflow is now a supported destination for native OpenTelemetry export from the Claude platform, and trace data from the Claude platform can be exported directly to Databricks MLflow. By default, the export does not include input and output content; users must set content mode to "full" for it to be collected. Databricks also mentions that MLflow Issues is in Beta, using Genie Code to identify recurring quality and operational issues.
AI overview based on source reports · Updated 2 days ago
Coverage timeline
Follow the coverage to explore different perspectives.
- Databricks BlogClaude Platform now supports native OpenTelemetry observability in Databricks MLflow
Databricks MLflow is now a supported destination for native OpenTelemetry export from the Claude Platform, letting developers using the Anthropic SDKs, the Messages API and Managed Agents send traces to Databricks for debugging and evaluation. Spans are received through Zerobus Ingest and stored in Unity Catalog tables linked to an MLflow experiment, where they can be inspected alongside traces from other instrumented services and queried with SQL. Setup involves creating an experiment, configuring the Databricks destination with workspace ID, region and spans table, then running a task and inspecting the trace.
Activity for this story
- Current comparable activity
- 3
- Peak comparable activity
- 10Nov 4 05:00
- Change in the past 24 hours
- -49%
Trends compare the same fully observed participants, which may cover fewer participants than current activity. Move the pointer or tap the chart to inspect hourly activity; use the left and right arrow keys with a keyboard.