{{ message }}
Repository navigation
[bugfix] handle empty metric rows on the monitor detail page - #4464
Merged
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
2 participants
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.
What's changed?
Fixes #4460.
In HertzBeat 1.9.0, metrics that return zero rows can have a null
valueRowsfield. The monitor detail page accessesvalueRows.lengthwhen processing the response and rendering pagination, causing runtime errors that interrupt page rendering and affect navigation to historical charts.Default null or undefined
valueRowsto an empty array so empty metrics can display the existing no-data state without disrupting the monitor detail page.Screenshot
Checklist
Add or update API