refactor: clarify running status diagnostics - #180
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
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.
Pull Request
Description
Reorganizes the running status page around the current operational result before supporting diagnostics. Adds a compact cluster summary, routes peer and storage diagnostics into cluster health, surfaces stale or degraded usage data beside scanner metrics, and moves raw diagnostic sources into a compact collapsible section. Missing optional diagnostics are no longer rendered as five synthetic
not_reportedrows.Type of Change
Testing
Checklist
Related Issues
N/A
Screenshots (if applicable)
A local static design preview was reviewed before implementation. Runtime screenshot capture requires a connected RustFS backend and authenticated admin session; the standalone development server redirects
/statusto/403when those services are unavailable.Additional Notes
not_reportedremains a neutral optional-source state and does not by itself mark the cluster unhealthy.