Cherry-pick #22237 to 7.x: [Metricbeat] Remove io.time from windows#22313
Merged
fearful-symmetry merged 2 commits intoelastic:7.xfrom Oct 30, 2020
Merged
Cherry-pick #22237 to 7.x: [Metricbeat] Remove io.time from windows#22313fearful-symmetry merged 2 commits intoelastic:7.xfrom
fearful-symmetry merged 2 commits intoelastic:7.xfrom
Conversation
* remove io.time from windows * fix tests * add changelog entry (cherry picked from commit 77882fc)
Contributor
|
Pinging @elastic/integrations (Team:Integrations) |
Contributor
Contributor
💚 Flaky test reportTests succeeded. Expand to view the summary
Test stats 🧪
|
kaiyan-sheng
approved these changes
Oct 30, 2020
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.
Cherry-pick of PR #22237 to 7.x branch. Original message:
What does this PR do?
It looks like
diskio.io.timeis a unix-only field that reports an incorrect zero. We accidentally marked it as "no incorrect zero" on our massive spreadsheet of metrics inventory, so it was overlooked until now.Why is it important?
We don't want to report "incorrect zero" metrics.
Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.How to test this PR locally
diskiometricset and insure thatdiskio.io.timeis not reported.diskio.io.timeis reported.Related issues