Show live DSP resource and backup usage in Diagnostics - #3
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.
The Platform Owner Diagnostics page now shows live per-DSP CPU, RAM, worker/task counts, storage usage and backup totals. CPU/RAM refresh every two seconds; storage and completed backup metadata refresh asynchronously every minute, with timestamps and explicit stale/unavailable states.
Resource totals include each DSP's isolated plugin and browser workers. Cards distinguish manual backups, DSP update snapshots and plugin rollback copies, and show runtime storage separately. Shared Core overhead is excluded. DSP members and scoped DSP views cannot access these metrics.
Validation: source checks and both product builds; CPU delta/restart, worker attribution, backup isolation/cache/symlink/failure tests; API access and path-redaction checks; Playwright live polling, stale state, desktop/mobile layout and authorization checks. A read-only host check confirmed successful storage/backup measurements for both active DSPs. No release or installation is included.