Skip to content
New issue

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

Tracing integrations: allow for custom trace/run_ids #1264

Open
marcklingen opened this issue Dec 24, 2024 · 0 comments
Open

Tracing integrations: allow for custom trace/run_ids #1264

marcklingen opened this issue Dec 24, 2024 · 0 comments
Labels
feature request Ideas to improve an integration

Comments

@marcklingen
Copy link
Contributor

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:

  • add additional non-haystack spans to the trace
  • record user feedback or other evaluation metrics for the trace
  • be able to fetch the single trace via API at a later point
  • use distributed tracing to log to the same trace id

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.

@marcklingen marcklingen added the feature request Ideas to improve an integration label Dec 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Ideas to improve an integration
Projects
None yet
Development

No branches or pull requests

1 participant