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

vmware exporter reports as not successful but metrics are reported (v0.30.0-rc.1) #1788

Closed
aa-matthias opened this issue Nov 30, 2024 · 4 comments · Fixed by #1791
Closed
Labels

Comments

@aa-matthias
Copy link

aa-matthias commented Nov 30, 2024

Current Behavior

After testing v0.30.0-rc.1 (#1774 ✌️) vmware collector is reporting no success but metrics are collected.

windows_exporter_collector_success{collector="vmware"} 0
windows_exporter_collector_timeout{collector="vmware"} 0
windows_exporter_collector_duration_seconds{collector="vmware"} 0

but:

windows_vmware_host_processor_speed_mhz 2594

Expected Behavior

shouldn't it have been successful? I cannot see any errors in the windows event log as well.

Steps To Reproduce

No response

Environment

  • windows_exporter Version: 0.30.0-rc.1
  • Windows Server Version: 2019

windows_exporter logs

nothing beeing logged in eventlog

Anything else?

No response

@aa-matthias
Copy link
Author

aa-matthias commented Nov 30, 2024

I do see that memory metrics are missing, only cpu collector is reporting anything. - rebuilding performance counters hasn't helped.

@aa-matthias aa-matthias changed the title vmware exporter reports as not successful but metrics are reported (v0.30.0rc1) vmware exporter reports as not successful but metrics are reported (v0.30.0-rc.1) Nov 30, 2024
@jkroepke
Copy link
Member

While refactor the vmware collector, there was a lot of guessing, since I found no docs.

The error should be logged on DEBUG level and on application start.

Could you run typeperf -qx to generate a list of metrics and attach it?

@aa-matthias
Copy link
Author

not sure but i think these are the ones (german locale here, sorry).

\VM-Prozessor(_Total)\Limit in MHz
\VM-Prozessor(_Total)\Reservierung in MHz
\VM-Prozessor(_Total)\Anteile
\VM-Prozessor(_Total)\CPU stolen time
\VM-Prozessor(_Total)\Prozessorzeit (%)
\VM-Prozessor(_Total)\Effektive VM-Geschwindigkeit in MHz
\VM-Prozessor(_Total)\Hostprozessorgeschwindigkeit in MHz
\VM-Arbeitsspeicher\Aktiver Arbeitsspeicher in MB
\VM-Arbeitsspeicher\Arbeitsspeicher-Balloon in MB
\VM-Arbeitsspeicher\Arbeitsspeicherlimit in MB
\VM-Arbeitsspeicher\Zugeordneter Arbeitsspeicher in MB
\VM-Arbeitsspeicher\Arbeitsspeicher-Overhead in MB
\VM-Arbeitsspeicher\Arbeitsspeicherreservierung in MB
\VM-Arbeitsspeicher\Gemeinsamer Arbeitsspeicher in MB
\VM-Arbeitsspeicher\Eingesparter gemeinsamer Arbeitsspeicher in MB
\VM-Arbeitsspeicher\Arbeitsspeicheranteile
\VM-Arbeitsspeicher\Abgerufener Auslagerungsspeicher in MB
\VM-Arbeitsspeicher\Memory Target Size
\VM-Arbeitsspeicher\Belegter Arbeitsspeicher in MB

@aa-matthias
Copy link
Author

confirmed to be fixed with v0.30.0-rc.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants