Cherry-pick #23413 to 7.11: libbeat/cmd/instance/metrics: fix error message#23415
Merged
axw merged 1 commit intoelastic:7.11from Jan 13, 2021
Merged
Cherry-pick #23413 to 7.11: libbeat/cmd/instance/metrics: fix error message#23415axw merged 1 commit intoelastic:7.11from
axw merged 1 commit intoelastic:7.11from
Conversation
Upon failure to retrieve cgroup stats, the log message should say "error getting cgroup stats" and not "error getting group status". (cherry picked from commit 8e8bfc8)
Contributor
|
Pinging @elastic/integrations-services (Team:Services) |
Contributor
kaiyan-sheng
approved these changes
Jan 12, 2021
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 #23413 to 7.11 branch. Original message:
What does this PR do?
Upon failure to retrieve cgroup stats, the log
message should say "error getting cgroup stats"
and not "error getting group status".
Why is it important?
Because the invalid log message is confusing.
Checklist
- [ ] I have commented my code, particularly in hard-to-understand areas- [ ] I have made corresponding changes to the documentation- [ ] I have made corresponding change to the default configuration files- [ ] I have added tests that prove my fix is effective or that my feature works- [ ] I have added an entry inCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.How to test this PR locally
N/A (trivial change)
Related issues
https://github.com/elastic/beats/pull/21113/files#r554442805