Cherry-pick #17272 to 7.x: Fix Disk Used and Disk Usage visualizations in the Metricbeat System dashboard #17285
Conversation
This file contains 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
…dashboard (elastic#17272) * fix * changelog (cherry picked from commit ac7aa9d)
narph
added
[zube]: In Review
backport
Metricbeat
|
Pinging @elastic/integrations (Team:Integrations) |
ChrsMark
approved these changes
Mar 27, 2020
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.
Cherry-pick of PR #17272 to 7.x branch. Original message:
What does this PR do?
Rewrites the Metricbeat System Overview and Metricbeat Host Overview dashboards, only updates the Disk Usage and Disk used visualizations.
Why is it important?
Fixes #12435
Detailed explanation here #12435 (comment)
The TSVB will in all visualizations except the time series will only show the value of the last data and not the data of the selected time range. So, if no documents are found in the last bucket, value will be 0. Increasing the bucket interval in order to include at least one meaningful doc will fix the issue.
The 2 visualizations are populated by data from the
fsstatmetricset which by default has a higher interval, so the visualizations were rarely showing any results.The visualizations reflect the last value and will search over all the documents selected in the timepicker.
Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.