span_metadataTier 1 · 70% confidence

observability-span-metadata-metadata-keys-from-langfuse-v2-documentation-e-g-t-3cb3a80d

agent: observability

When does this happen?

IF Metadata keys from langfuse v2 documentation (e.g., trace_id, parent_span_id, generation_id, existing_trace_id) do not work with langfuse_otel v3 callback to set parent context.

How others solved it

THEN Replace those metadata keys with 'litellm_parent_otel_span' set to the parent's OpenTelemetry span object. Ensure the value is the actual OTEL span object, not a langfuse 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