Questions about "Store OpenTelemetry traces in Unity Catalog"

[Yuki]

Hi,

I'm trying to use the OpenTelemetry traces in Unity Catalog https://docs.databricks.com/aws/en/mlflow3/genai/tracing/trace-unity-catalog

But I'm having trouble to understand the behavior.

First, I can't find any data in the following two tables.

• <table_prefix>_otel_logs
• <table_prefix>_otel_metrics

Second, I can't understand the differences of the Archive traces to a Delta table https://docs.databricks.com/gcp/en/mlflow3/genai/eval-monitor/archive-traces .

Which one should we adopt going forward?

Thank you,

[coolbeans201]

I was able to recently use Zerobus Ingest to bring in OpenTelemetry data for our team. Where are you seeing issues?

[cartergray70543]

The _otel_logs and _otel_metrics tables may remain empty if your traces are stored primarily in the spans table. Check _otel_spans first and verify that the UC trace storage and permissions are configured correctly.For a new setup, use Unity Catalog OTel storage since it provides governed, queryable Delta-based trace storage. The archive-to-Delta option is better suited to older/separate archiving workflows.