Fix high values of proc.cpu.user_p #1928
Merged
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
monicasarbu
force-pushed
the
fix_proc_cpu_1_3
branch
from
be2e998
to
11ccbe1
Compare
|
Meging, as appveyor fail in Winlogbeat cannot be related. |
| @@ -87,6 +87,7 @@ https://github.com/elastic/beats/compare/v1.2.2...v1.2.3[View commits] | |||
| *Topbeat* | |||
|
|
|||
| - Fix high CPU usage when using filtering under Windows. {pull}1598[1598] | |||
| - Fix high values of proc.cpu.user_p. {pull}1928[1928] | |||
There was a problem hiding this comment.
@monicasarbu I think this changelog entry was placed/merged to the wrong location, right? Shouldn't it be under the 1.3.0 section?
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.
Apply the same fix from #1128 to proc.cpu.user_p. This is fixed already in 5.0.