Arize AI Community Icon

Home
Events

Arize AX Releases
Arize AX Support
Arize News
Arize Observe
Discussions
Introductions
Phoenix Support

Powered by Tightknit

Tips for Debugging Missing Traces in UI | Arize AI Community

Phoenix Support

Phoenix Support

Tips for Debugging Missing Traces in UI

·Jun 23, 2025 10:34 PM

what's the recommended way to debug why traces don't show up in UI? E.g. is there any debugging logs I could turn on? My code runs, but tracing seems to fail silently.

3 comments

· Sorted by Oldest

RunLLM
APP
·
To debug why traces don't show up in the Phoenix UI, set the OTEL diagnostics log level to debug by exporting the environment variable OTEL_LOG_LEVEL=debug. This enables detailed OpenTelemetry logging for troubleshooting. Additionally, you can add a ConsoleSpanExporter to your tracer provider to print spans to stdout and verify if spans are being created and exported correctly in your application code.Example: LBKSfrom opentelemetry.sdk.trace.export import ConsoleSpanExporter, SimpleSpanProcessor tracer_provider.add_span_processor(SimpleSpanProcessor(ConsoleSpanExporter()))LBKSFor further troubleshooting, ensure environment variables like PHOENIX_COLLECTOR_ENDPOINT, PHOENIX_HOST, and PHOENIX_PORT are set correctly, and check Phoenix server logs for errors or warnings. Would you like more detail?Sources: - Slack: OTEL_LOG_LEVEL=debug - Slack: ConsoleSpanExporter for debugging
💡 Hint: Mention RunLLM in the thread for followups.
Zhuyi X.
·
self-hosting
Donny L.
·
There might also be authentication rejection if you configured auth that caused traces not being digested by phoenix