newrelic / nri-winservices

Windows services Integration for New Relic Infrastructure
Apache License 2.0
8 stars 8 forks source link

windows_exporter.exe high CPU load #123

Closed philhub82 closed 2 years ago

philhub82 commented 2 years ago

Description

windows_exporter.exe uses over 50% of CPU after a few seconds when NewRelic service starts. CPU is then going up and down but slows down the server tremendously. image

NR Diag results

I sent the NR Diag Report to support and they wrote me: Upon reviewing the diagnostic log, we were able to see that your specific Windows Exporter is being used by nri-winservices:

time="2022-04-06T09:41:15+02:00" level=debug msg="event excluded by metric matcher" component=AgentContext entity_key= event="+&{{ProcessSample 1649230875 } windows_exporter.exe

As this exporter is related to a feature currently in Beta, our recommendation moving forward is to lodge this as an Issue to the Windows services GitHub:

Steps to Reproduce

It happens as soon as the NR service starts.

Your Environment

NR Infra Agent 1.24.0.0

VMWare Windows Server 2019 2 CPUs 4GB RAM

winservices-config.yml integrations:

Additional context

carlossscastro commented 2 years ago

Hi @philhub82,

Thanks for reaching out. Could you please run from command prompt/powershell the following command and paste here the output:

C:\Program Files\New Relic\newrelic-infra\newrelic-integrations\windows_exporter --version

We just want to make sure you are running the latest version of the exporter.

Rg,

philhub82 commented 2 years ago

c:\Program Files\New Relic\newrelic-infra\newrelic-integrations>windows_exporter.exe --version windows_exporter, version 0.18.1 (branch: heads/tags/v0.18.1, revision: e07b2053af3ca708db3489f41e2fcde9941860f4) build user: runneradmin@fv-az177-985 build date: 20220205-08:18:35 go version: go1.17.6 platform: windows/amd64

carlossscastro commented 2 years ago

Hi @philhub82 ,

Thanks for the info. The version of the exporter is not the one shipped with our infra agent. I would suggest deleting the C:\Program Files\New Relic\newrelic-infra\newrelic-integrations\windows_exporter.exe manually and reinstalling our latest version of the agent to ensure you have the correct windows exporter version. You can download the agent directly from here: http://download.newrelic.com/infrastructure_agent/windows/newrelic-infra.msi

Note that some cpu usage is expected when the agent invokes the exporter to obtain metrics, every 30 seconds (by default).

Let us know how this works out for you.

Thanks

philhub82 commented 2 years ago

we started to have this problem with the original Version and then tried with the newest one. but it was the same problem before.

davidgit commented 2 years ago

We appreciate you taking the time to bring this to our attention. After reviewing this issue, we are unable to commit on a timeline to resolution. When committing to resolve an issue, we take into account the type of issue, the customer impact, and the development effort required.

In this specific case, the issue would require investigating if the community windows prometheus exporter our integration is built on top of has some performance issues. Sadly, we haven't experienced those issue, neither have the community.

We would encourage you to increase number of CPUs/RAM.

If the situation changes, we will revisit this decision. If you have any further questions or comments about this, please let us know by replying to this issue.