feat: accept metadata transformer for LangChain callback handler#516
Merged
Conversation
whoseoyster
approved these changes
Aug 29, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Pull Request
Summary
Introduces an optional kwarg
metadata_transformerto the LangChain callback handler.metadata_transformershould be a transformation function (Callable[[Dict[str, Any]], Dict[str, Any]]) that is applied to the metadata object currently logged by the callback handler. This gives the user fine-grained control about the metadata logged.Correctly parses usage information when streaming responses
The previous version of the callback handler didn't have the
on_new_tokenmethod implemented. The current implementation handles the usage information, which is streamed at the very end whenstream_usage=True.Context logging
Now, we're correctly logging the context on retrieval steps as well as on chains that contain
source_documents. This enables context-dependent metrics on the platformUsage
For example, if the user wants to exclude metadata fields that start with
langgraph, a possible metadata transformer would be:For streaming, the usage is: