feat: add cache-token fields to set_usage - #65
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
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.
RIUS-541 (Python half; TS mirror in rius-sdk-typescript).
Extends
Generation.set_usagewith two optional fields for cache-read and cache-creation input tokens, emitted asgen_ai.usage.cache_read.input_tokens/gen_ai.usage.cache_creation.input_tokensper OTel GenAI semconv.Per the convention,
gen_ai.usage.input_tokensis the total including cached tokens (cache counts are subsets). Callers pass provider-reported values as-is; the sink normalizes Anthropic's exclusiveinput_tokens(core sub-ticket).Tests: 228 passed, 7 skipped.