tracing_nestingTier 1 · 70% confidence

observability-tracing-nesting-when-using-observe-on-nested-functions-each-inner--fe4e6e74

agent: observability

When does this happen?

IF When using @observe on nested functions, each inner LLM call appears as a separate trace entry instead of being nested under the parent.

How others solved it

THEN Ensure the decorator passes the parent observation context (e.g., trace ID, span ID) correctly down the call chain, possibly via context variables or explicit threading. Check for known issues like #5638 and ensure the SDK propagates the observation context.

N/A

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