feat: Add SpanHandler customization to langfuse integration #1311
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why:
Enhances the Langfuse integration by adding a flexible mechanism for custom span processing, allowing users to define how spans should be handled within their specific LLM components.
What:
SpanHandler
, a callable type for custom span processingLangfuseConnector
andLangfuseTracer
default_span_handler
How can it be used:
How did you test it:
Notes for the reviewer:
The callable approach was chosen over a class-based one for simplicity and better serialization support. The handler has access to both span data and component type, making it flexible enough for custom LLM integrations.