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

[BUG] there is no *windows_physical_disk_free_bytes* #1896

Closed
chuwza opened this issue Feb 22, 2025 · 2 comments · Fixed by #1897
Closed

[BUG] there is no *windows_physical_disk_free_bytes* #1896

chuwza opened this issue Feb 22, 2025 · 2 comments · Fixed by #1897

Comments

@chuwza
Copy link

chuwza commented Feb 22, 2025

Hi, I tested windows_exporter version 30.4, version 28.2. I can confirm that this problem can be reproduced stably, you can test it on your own Windows 10/11 computer, it only takes 1 minute!

I'm not using windows_exporter config.yml, everything's default. I just and boot ./windows_exporter-0.30.4-amd64.exe in powershell, and access http://192.168.1.2:9182/metrics.

And I can't found windows_physical_disk_free_bytes
Image

But in the documentation, We can see that there is indeed this metric
https://github.com/prometheus-community/windows_exporter/blob/master/docs/collector.physical_disk.md#alerting-examples
Image
Image

Why? How can I let windows_exporter to collect windows_physical_disk_free_bytes?

@chuwza chuwza changed the title Why I don't have *windows_physical_disk_free_bytes*? [BUG] there is no *windows_physical_disk_free_bytes* Feb 22, 2025
@jkroepke
Copy link
Member

The docs are incorrect. You are looking for windows_logical_disk_free_bytes and windows_logical_disk_size_bytes

@chuwza
Copy link
Author

chuwza commented Feb 22, 2025

The docs are incorrect. You are looking for windows_logical_disk_free_bytes and windows_logical_disk_size_bytes

Okay, I understand, thank you very much!

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

Successfully merging a pull request may close this issue.

2 participants