Replies: 3 comments 1 reply
-
@MrOrz, agree that an "official" solution to distributed tracing when using the decorator-based integration is helpful here. I'd recommend to use the rootTraceId-based workaround suggested by @hassiebp in the meantime. Does it work for you? |
Beta Was this translation helpful? Give feedback.
-
I tried using Setting trace ID via |
Beta Was this translation helpful? Give feedback.
-
@MrOrz We have just released support for distributed tracing via passing a Langfuse parent ID. Please check out our release and docs and curious to hear whether all works for you 👍🏾 |
Beta Was this translation helpful? Give feedback.
-
Describe the feature or potential improvement
I love the simplicity of Python Decorator SDK and would like to incorporate distributed tracing with it.
In our setup, we have LLM apps that would call Tools, with both types of microservices linked to the same Langfuse project. LLM apps would pass the current Langfuse trace ID and observation ID to Tools when the LLM app decide to call tools.
Currently, we are able to set custom trace ID by passing
langfuse_observation_id
kwarg to the first method that is wrapped by@observe
in Tools. However, we can't do the same as we also want to setparent_observation_id
. Although it is possible to set it through the low-level SDK, seems that if we choose to use decorators we just can't achieve the same.What is the recommended way to set parent observation ID through the decorator based Python SDK? A documentation / snippet on the recommended way to do Distributed Tracing between the Tool and LLM apps would be helpful too.
Additional information
Original Discord thread: https://discord.langfuse.com/m/1278314469960974379
Other related discussions
Beta Was this translation helpful? Give feedback.
All reactions