Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Metricbeat]System/process metricset - WmiPrvSE.exe seems to utilize more CPU on v 7.0.0 #11840

Closed
narph opened this issue Apr 16, 2019 · 0 comments · Fixed by elastic/gosigar#116
Closed

[Metricbeat]System/process metricset - WmiPrvSE.exe seems to utilize more CPU on v 7.0.0 #11840

narph opened this issue Apr 16, 2019 · 0 comments · Fixed by elastic/gosigar#116
Assignees
@narph
Labels
Metricbeat Metricbeat Team:Integrations Label for the Integrations team :Windows

Comments

@narph
Copy link
Contributor

narph commented Apr 16, 2019 •
edited
Loading

  • Version: Compared Metricbeat 6.7.1 with 7.0.0
  • Operating System: Windows Server 2016
  • Steps to Reproduce:
    Enabled only the system process metricset:
- module: system
  period: 10s
  metricsets:
    #- cpu
    #- load
    #- memory
    #- network
    - process
    #- process_summary
    #- socket_summary
    #- core
    #- diskio
    #- socket
  enabled: true
  processes: ['.*']

When running Metricbeat v6.7.1 we see the following in the Performance Monitor tool:

671

6711

When running with the v 7.0.0:
700

7001

We notice the WMI provider host process is using more CPU when running Metricbeat v 7.0.0 than while running earlier versions of Metricbeat
@exekias exekias added the Team:Integrations Label for the Integrations team label Apr 16, 2019
narph added a commit to narph/gosigar that referenced this issue Apr 18, 2019
@narph
Remove wmi queries with win32 api calls
43bc214 
Fixes elastic/beats#11840

Addresses high CPU load on windows
@narph narph mentioned this issue Apr 18, 2019
Merged
@narph narph self-assigned this Apr 19, 2019
narph added a commit to elastic/gosigar that referenced this issue Apr 24, 2019
@narph
Replace wmi queries with win32 api calls (#116)
ab1e753 
* Remove wmi queries with win32 api calls

Fixes elastic/beats#11840

Addresses high CPU load on windows

* Add more tests

* Add more tests for coverage

* Add tests

* Add tests for coverage

* Remove WIn32Process related structs

* Fix test failing on osx

* Work on tests

* Clean up tests

* Fix on changelog file
@narph narph reopened this Apr 24, 2019
@zube zube bot added [zube]: Inbox and removed [zube]: Done labels Apr 24, 2019
@narph narph mentioned this issue Apr 24, 2019
Merged
@narph narph closed this as completed Apr 25, 2019
@zube zube bot added [zube]: Done and removed [zube]: Inbox labels Apr 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@narph narph

Labels
Metricbeat Metricbeat Team:Integrations Label for the Integrations team :Windows
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Replace wmi queries with win32 api calls narph/gosigar
3 participants
@exekias @narph @alvarolobato