Replies: 1 comment 5 replies
-
|
Based on the sources, the issue you're experiencing is related to how trace names are determined when using the How Trace Names WorkWhen using Solution: Use
|
Beta Was this translation helpful? Give feedback.



Uh oh!
There was an error while loading. Please reload this page.
-
Description
I’m trying to understand how the top-level trace name is determined when using the Langfuse Python SDK.
In the example below, the top-level trace name in the Langfuse UI always appears as process_task, even though the first executed function (and the one decorated with observe) is main. I also tried updating the trace name with update_current_trace(name="Demo"), but it didn’t change the displayed name of the top-level trace.
Question
How can I ensure that the top-level trace name in Langfuse reflects the first executed span (main) or a custom name (e.g., "Demo") instead of the function name of a child span like process_task?
Environment
Beta Was this translation helpful? Give feedback.
All reactions