I love the VMware Virtual Machine (SOAP) sensor as it shows a lot of detail that is VM-specific. However, when a VM moves from host to host I end up getting a "Down" alert on the source host telling me the VM can't be found, and I do not see away for the destination host to monitor the VM.

I can see this being especially troubling when I do patching of my hosts, because literally every VM will move once or twice during the process. Is there an automated way of accounting for the portability of VM's with this particular sensor?

Article Comments

Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.

Hi,

please add your vCenter Server as a device in PRTG. Then add the VMWare Virtual Machine Sensors to this device. This will ensure that migration of VMs through VMotionwill not cause miss-alarms, or show false states on the VMs.


Feb, 2015 - Permalink

Will it be possible to migrate the VM's sensory history as well, or will it all be lost?


Sep, 2016 - Permalink

Since it's a different sensor, the history will be lost. The easiest way would be to pause the historic sensors and keep them for reporting. Then simply re-add the sensors to the device and they'll start monitoring from there on out.


Oct, 2016 - Permalink