fix: extract token usage from mappings - #1433
Open
KXHXK wants to merge 1 commit into
Open
Conversation
KXHXK
marked this pull request as ready for review
July 26, 2026 10:19
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
1 participant
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
Fixes #1432.
TokenUsageExtractornow reads token fields from both mapping-backed usage metadata and attribute-based provider objects. This prevents dictionary-shapedusageandusage_metadatapayloads from silently producing empty token telemetry.The change also replaces the mocked mapping streaming test with an end-to-end extractor path, while retaining explicit regression coverage for object-backed usage.
Testing
tests/unit/instrumentation/common: 59 passedruff checkon changed filesruff format --checkon changed filesmypy agentops/instrumentation/common/token_counting.pygit diff --check