add: count total tokens for trace runs #73
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.
Summary
This PR introduces the functionality to count the total tokens used during trace runs in the tracer.py module. This enhancement allows for better tracking and management of token usage across different API calls, providing valuable insights for performance and cost analysis.
Changes Made
Added logic to aggregate total token counts from LLM API calls within the save method of the TraceClient class.
The implementation captures prompt tokens, completion tokens, and total tokens for each trace entry, ensuring accurate reporting.
Created tests in test_traces.py to validate the total token aggregation functionality.
Testing
Ran all tests in test_traces.py to verify the correctness of the token counting functionality.
All tests passed successfully, confirming that the new feature works as intended and does not introduce any regressions.