fix(monitoring): show account cache read and write metrics#340
Merged
Conversation
Render the existing account cache slot as C, CR, and CW based on the available token buckets. Apply the same compact presentation to desktop token structure, mobile cards, and model details without changing responsive layout. Preserve legacy cached-token display and cover fine-grained, mixed, and empty cache states.
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
Fix the request-monitoring account overview so its cache slot displays fine-grained cache reads and writes instead of showing zero when legacy cached tokens are absent.
The responsive layout remains unchanged and legacy cache-only models keep their existing presentation.
Scope
Changes
User Impact
GPT-5.6 account summaries no longer show cache usage as zero when requests contain cache reads or cache writes. Users can distinguish cache hits from cache creation directly in both desktop and mobile monitoring views.
Compatibility / Runtime Notes
Data / Security Notes
N/A. No persistence, authentication, key handling, raw usage data, or export behavior changes.
Risk / Rollback
Risk level: Low
Rollback notes:
c00daa9.Verification
Commands / evidence:
Frontend result: 86 test files, 741 tests passed.
Screenshots / Recordings
Not captured. Server-rendered component tests verify the desktop table and shared responsive cache presentation for C, CR, and CW states.
Docs
Related
Refs #338