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.

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 metrics populating on one Windows server, but not the other? #1014

Closed
m0ussaka opened this issue Jul 1, 2022 · 3 comments
Closed

Comments

@m0ussaka
Copy link

m0ussaka commented Jul 1, 2022

Preface: New to Prometheus and windows_exporter. Trying to figure out why I'm getting certain metrics from one server, but not the other. Is there a way to force the population of certain values?

Both servers are 2012R2
Running version 0.18.1 installed with default values from the .msi

While searching /metrics page on each machine, I'm missing these values on one that are causing No Data to show on my dashboard.

windows_os_physical_memory_free_bytes
windows_os_processes
windows_os_time

I saw in another topic someone asked to make sure the os collector is running. How do I do this?

@breed808
Copy link
Contributor

breed808 commented Jul 2, 2022

The os collector is a default collector, so it will be enabled as you've installed with default values.

While some of these could be unavailable due to underlying issues, the windows_os_time metric is provided by currentTime.Unix() which makes its absence quite unusual.

Are there any major differences between these two hosts? E.G. operating system version, installed components, etc.
It would also be worth checking the value of the windows_exporter_collector_success metric to see if the os collector is failing. Enabling debug output for the exporter might provide additional troubleshooting information.

@thierryVCL
Copy link

Hello We have the same issue . In our case it's related to an invalid configuration of the swap ( one page file is declared on a non existing drive) which make the os collector not completing its collection.
The fix was already provided and is merged : #939.
I guess it should be included in the next release. When do you plan to release the next version of the windows_exporter ?

Thanks

@m0ussaka
Copy link
Author

m0ussaka commented Jul 7, 2022

Thanks for the info. I guess I'll just hold off and hope the new version pushes out soon.

@breed808 I see windows_exporter_collector_success{collector="os"} 0
Assuming that means it hasn't started.
Much like the other issue linked, I'm seeing Event ID 102 with it stating, "The system can't find the file specified." Assuming it is referencing the page file.

@m0ussaka m0ussaka closed this as completed Jul 7, 2022
@m0ussaka m0ussaka reopened this Jul 7, 2022
@m0ussaka m0ussaka closed this as completed Jul 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants