fix(monitoring): parse wrapped tenant server info - #204
Open
GatewayJ wants to merge 1 commit into
Open
Conversation
Member
Author
GatewayJ
marked this pull request as ready for review
July 29, 2026 16:02
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.
Type of Change
Related Issues
Fixes #199
Summary of Changes
infofield instead of silently accepting an empty server-info snapshot.1.0.0-beta.10.The Operator previously parsed the entire
/rustfs/admin/v3/inforesponse as the inner server-info object. Since the modeled fields have Serde defaults, the response envelope was accepted as an empty value and the poll was reported as successful with every derived Tenant metric set to zero.Checklist
make pre-commit(fmt-check + clippy + test + console-lint + console-fmt-check)[Unreleased](not updated)Impact
Verification
Additional Notes
No configuration or CRD changes are required.
Thank you for your contribution! Please ensure your PR follows the community standards (CODE_OF_CONDUCT.md) and sign the CLA if this is your first contribution.