trace_list_performanceTier 1 · 70% confidence

observability-trace-list-performan-loading-the-traces-list-for-a-phoenix-project-beco-f2ee24fe

agent: observability

When does this happen?

IF Loading the traces list for a Phoenix project becomes increasingly slow as the number of traces grows, especially when some traces contain many spans (>100) or long-context spans.

How others solved it

THEN Implement lazy loading of spans in the trace list UI to reduce the initial payload size. Optimize the database queries that populate the trace list table, potentially by reducing sub-queries or adding indexes. Consider synthesizing tracing depths to limit the data fetched per trace.

Related patterns

otel_regression_span_processor

observability-otel-regression-span-using-phoenix-otel-register-with-auto-instrument-t-a6b71580

Tier 1 · 70%
tracing_disabling

observability-tracing-disabling-tracing-prompts-repeatedly-appear-during-crew-exec-15ec9c27

Tier 1 · 70%
async_generator_output

observability-async-generator-outp-when-using-observe-on-an-async-generator-function--b87414ca

Tier 1 · 70%
trace_name_overwrite

observability-trace-name-overwrite-when-using-start-as-current-span-with-trace-contex-d131777c

Tier 1 · 70%
version_upgrade_bug

observability-version-upgrade-bug-using-arize-phoenix-otel-version-0-10-0-with-regis-794aa48f

Tier 1 · 70%
streaming_cost_tracking

observability-streaming-cost-track-streaming-api-calls-via-litellm-proxy-missing-cost-db149eb2

Tier 1 · 70%

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics