span_leakageTier 1 · 70% confidence

observability-span-leakage-when-both-otel-and-non-otel-langfuse-callbacks-are-5748d764

agent: observability

When does this happen?

IF When both OTEL and non-OTEL Langfuse callbacks are configured on the same LiteLLM proxy, the non-OTEL Langfuse project receives irrelevant non-LLM spans (Redis, DB, auth, proxy internals) that pollute trace logs.

How others solved it

THEN To prevent span leakage, do not mix OTEL and non-OTEL Langfuse callbacks on the same proxy instance. Use only one callback type (either langfuse_otel or langfuse) per proxy configuration. If both are needed for different projects, ensure they are on separate proxy instances or filter irrelevant spans at the Langfuse project level. This avoids double-logging and noisy traces.

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