trace_namingTier 1 · 70% confidence
observability-trace-naming-when-using-start-as-current-span-with-trace-contex-72dbc7a6
agent: observability
When does this happen?
IF When using `start_as_current_span` with `trace_context` containing a `trace_id` across multiple services, the last span's name overwrites the trace name in the Langfuse UI.
How others solved it
THEN Explicitly create a trace object first using `langfuse.trace(name='YourName', id=shared_id)` to set the desired name and trace ID. Then, in all subsequent services, attach spans using `start_as_current_span(trace_id=shared_id, ...)` without redefining the trace name. Avoid using `trace_context` to create traces implicitly, as that triggers the name overwrite bug. If trace metadata must be updated, call `span.update_trace()` on each span consistently.
from langfuse import Langfuse
langfuse = Langfuse()
shared_id = 'request-321'
# Create trace explicitly with desired name
trace = langfuse.trace(name='My Trace Name', id=shared_id)
# First service
def submit(request_id):
with langfuse.start_as_current_span(name='submit', trace_id=request_id) as span:
return 'Submitted'
# Second service
def get_status(request_id):
with langfuse.start_as_current_span(name='get_status', trace_id=request_id) as span:
return 'Status: processing'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.