trace_nestingTier 1 · 70% confidence

observability-trace-nesting-using-langfuse-otel-callback-with-litellm-calls-ar-12caeb4f

agent: observability

When does this happen?

IF Using langfuse_otel callback with litellm, calls are not nested under parent spans, resulting in separate traces.

How others solved it

THEN Propagate the parent span context by passing the parent's OpenTelemetry span object via the metadata parameter 'litellm_parent_otel_span'. Create a child span from the langfuse client (or from any span that has an _otel_span attribute) and provide that to the completion call.

subspan = langfuse_client.start_span(name='litellm_generation_span')
completion(model='...', messages=[...], metadata={'litellm_parent_otel_span': parent_span._otel_span})

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