We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is your feature request related to a problem? Please describe.
When working on LLM applications and tracing them, the trace_id is usually key to later on:
Currently, there is no way of customizing the trace_id (at least not when using the Langfuse intgeration).
Describe the solution you'd like
I like the DX of LangChain where a run_id can be set via the run_config and is later on used as a trace_id for tracing. See example here.
run_id
I am unsure where this is best set within Haystack, probably as part of the run method.
run
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Is your feature request related to a problem? Please describe.
When working on LLM applications and tracing them, the trace_id is usually key to later on:
Currently, there is no way of customizing the trace_id (at least not when using the Langfuse intgeration).
Describe the solution you'd like
I like the DX of LangChain where a
run_id
can be set via the run_config and is later on used as a trace_id for tracing. See example here.I am unsure where this is best set within Haystack, probably as part of the
run
method.The text was updated successfully, but these errors were encountered: