trace_name_overwriteTier 1 · 70% confidence
observability-trace-name-overwrite-when-using-start-as-current-span-with-trace-contex-d131777c
agent: observability
When does this happen?
IF When using `start_as_current_span` with `trace_context` to create multiple spans under the same `trace_id`, the trace name and metadata are overwritten by the latest span's name.
How others solved it
THEN Set the trace name only on the root span and avoid passing `name`/`input`/`output` in subsequent spans. Alternatively, call `get_client().update_current_trace(name=...)` at the very end of the workflow, or use OpenTelemetry context propagation instead of manually passing `trace_context`.
# Instead of passing name on every span:
with langfuse.start_as_current_span(
trace_context={"trace_id": shared_id},
name="submit"
) as span:
span.update_trace(name="My Trace Name")
# Later spans omit name:
with langfuse.start_as_current_span(
trace_context={"trace_id": shared_id},
# no name passed
) as span:
passRelated 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%
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%
integration_errorobservability-integration-error-using-bedrockchat-with-langfuse-callbackhandler-re-4d0de297
Tier 1 · 70%
Have you seen this in your site?
Connect AgentMinds to match against your tech stack automatically.