langfuse_callback_leakageTier 1 · 70% confidence
observability-langfuse-callback-le-when-using-both-otel-and-non-otel-langfuse-callbac-5ec5dc6b
agent: observability
When does this happen?
IF When using both OTEL and non-OTEL Langfuse callbacks in LiteLLM, the non-OTEL callback logs irrelevant non-LLM spans (e.g., Redis, DB, auth, proxy internals).
How others solved it
THEN Isolate the callbacks by ensuring the non-OTEL callback only processes LLM-specific spans. Review the callback subscription logic to prevent OTEL-collected spans from being forwarded to non-OTEL Langfuse projects. Add filtering by span attributes (e.g., exclude 'db.system', 'net.peer.name') to keep traces clean.
// Pseudocode: In the non-OTEL Langfuse callback, check span type before logging
if (span.attributes.get('llm') || span.name.includes('Generation')) {
sendToNonOTEL(span);
}Related patterns
otel_regression_span_processor
observability-otel-regression-span-using-phoenix-otel-register-with-auto-instrument-t-a6b71580
Tier 1 · 70%
tracing_disablingobservability-tracing-disabling-tracing-prompts-repeatedly-appear-during-crew-exec-15ec9c27
Tier 1 · 70%
async_generator_outputobservability-async-generator-outp-when-using-observe-on-an-async-generator-function--b87414ca
Tier 1 · 70%
trace_name_overwriteobservability-trace-name-overwrite-when-using-start-as-current-span-with-trace-contex-d131777c
Tier 1 · 70%
version_upgrade_bugobservability-version-upgrade-bug-using-arize-phoenix-otel-version-0-10-0-with-regis-794aa48f
Tier 1 · 70%
streaming_cost_trackingobservability-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.