-
Notifications
You must be signed in to change notification settings - Fork 8
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.
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
Certain Service status and state not collected #128
Comments
Hello! The integration currently retrieves services data leveraging the windows prometheus exporter. Can you provide the
Then in the output we can check if those services are present.
|
Afternoon The following is the config.yml that I am trying to use, but I not see any metrics. Please advise where I am going wrong.
Output in PowerShell
envagent.txt
|
As @paologallinaharbur mentioned, we would need to check the output of the metrics endpoint from the exporter.
This will dump all the output to the screen. Alternatively you can redirect the output to a file:
Then grab that If you want to have a look at the output, each service will produce the following lines of info:
The above example is for the |
Thanks @carlossscastro Here are the details of the output through the browser when I specify just
However when I look at the output being generated from
|
Hello @markdavies71. We spotted the issue, since the exporter we are using calls the windows Api and tries to collect the services with the rights "SC_MANAGER_ALL_ACCESS", some restricted services can't be opened. We have opened the following PR to the windows exporter making the services to be opened with "GENERIC_READ", fixing the issue. prometheus-community/windows_exporter#1036 Once this PR is merged, we will bump the dependency in our integration and generate a new release. We will let you know as soon as the new release is done. |
Hello, we have just created the prerelease of the nri-winservices beta that is adding the exporter solving the issue. It will still not be added to the infrastructure-agent until next week, we will communicate it here once we do the infrastructure-agent release. |
The last released version of the agent https://github.com/newrelic/infrastructure-agent/releases/tag/1.29.0 is including the release of nri-winservices beta that solves this issue. |
Description
Metrics from certain services are not being collected and sent to New Relic
Expected Behavior
The status and startup metrics for all services configured within
winservices-config.yml
are captured and sent to New RelicSteps to Reproduce
The following are the services that I am trying to collect metrics from in the
winservices-config.yml
These are being parsed and recorded in the newrelic-infra.log
However only 13 services are returned, and not the 16 as listed in the yml file.
Your Environment
Windows Server 2019
New Relic Infrastructure Agent: v1.26.0
winservices.exe: v0.5.0-beta
tested config:
Additional context
The metric data is being capture and sent to New Relic for all the other 13 services listed in the yml file.
The text was updated successfully, but these errors were encountered: