-
Notifications
You must be signed in to change notification settings - Fork 203
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
Boot time metric doesn't show all running VMs #355
Comments
I've just discovered I have the exact same problem. The problem occurs when I migrate virtual machines to other nodes. The metrics simply disappear. |
I've got the same issue |
Same problem here, but with metric "vmware_vm_disk_usage_average". Also after doing vMotion on VM's during maintenance. vCenter version 7.0.3.01200. |
The project seems to have become rather stale, unfortunately. At least that's my feeling. The problem is that there aren't many other solutions. I'll probably have to find a way to actually understand what's happening and make some changes. Hopefully it isn't overly complicated. |
Also tried reading vSphere metrics with Telegraf docker container using the VMware vSphere Telegraf plugin and this output config to expose Prometheus values:
Having some more metrics with telegraf I also noticed:
Maybe this helps. Haven't looked into the code yet. For the moment I switched to using Telegraf as metrics exporter for vmware/vsphere. Scrape performance also seems to be comparable (scrape durations: vmware_exporter: 613.565ms vs. telegraf: 476.650ms). |
Hi, I have 73 VMs running but just 47 VM have boot time value. Anyone experience same issue?
Both exporter & prometheus are on k8s 1.25.4 with Image Tag v0.18.4 with following configuration:
The text was updated successfully, but these errors were encountered: