fix(monitoring): improve realtime request table clarity - #454
Merged
Conversation
Refine realtime request metrics, status diagnostics, and token usage details. Keep TPS based on total latency to avoid misleading generation-rate spikes. Improve compact table alignment and tooltip readability without changing stored data.
18 tasks
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
Improve realtime request table readability and restore TPS to the stable total-latency definition.
This removes misleading generation-rate spikes while keeping request timing and usage details accessible.
Scope
Changes
User Impact
Realtime request rows show a stable TPS value without misleading high generation-rate spikes.
Usage and failed-request details are easier to scan, while successful status cells stay concise.
Compatibility / Runtime Notes
Data / Security Notes
N/A. This PR changes frontend presentation and derived metrics only; persisted usage data and sensitive fields are unchanged.
Risk / Rollback
Risk level: Low
Rollback notes: Revert commit 844e67c to restore the previous realtime table presentation.
Verification
Commands / evidence:
Screenshots / Recordings
N/A — no browser automation runtime was available. The visible layout was iterated against user-provided screenshots.
Docs
Docs decision: This PR refines an existing realtime monitoring table and does not add a user-facing capability that requires documentation.
Related
Refs #453