Merged
Conversation
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.
Description
This pull request enhances the LLM response handling across all supported providers by adding token usage tracking. The
LLMResponseobjects returned by each LLM now include an optionalusagefield that provides detailed token counts for requests and responses. This enables better monitoring and analysis of LLM costs and performance.LLMUsagetype and updated imports and__all__insrc/neo4j_graphrag/llm/__init__.pyto expose it across the package.anthropic_llm.py,bedrock_llm.py,cohere_llm.py,mistralai_llm.py,ollama_llm.py,openai_llm.py) to extract token usage information from their respective API responses and include it in theLLMResponsevia the newusageparameter.Noneif unavailable, paving the way for uniform downstream handling and analytics.Type of Change
Complexity
Complexity: low
How Has This Been Tested?
Checklist
The following requirements should have been met (depending on the changes in the branch):