We are currently testing your system as an replacement for our current management system and we are experiencing some problems with the local core/probe health. It works fine when we have our network added, 37 devices and 352 sensors. But when adding two VMware ESX server the probe health seems to drop so we get a warning (2 devices and 128 sensors). The PRTG server have 4GB of RAM and a dual core 2.4GHz CPU.

What is the best practice in monitoring VMware servers?

Article Comments

Hello,

130 VMware sensor are quite an amount for one probe, respectively for the underlying SOAP-connection. Which scanning interval is set on the sensors? If possible, please try 5 minutes. Furthermore, if that does not help, please try or consider moving about half of the VMware sensors to an additional remote probe.

best regards.


Jun, 2011 - Permalink

Sat it to 2min now, thank you! I guess remote probes are the way to go when you have big VMware servers?


Jul, 2011 - Permalink

Changed the scanning interval now, still some problems now and then, but allot better than before. I guess that installing remote probes for big VMware servers is the best solution?


Jul, 2011 - Permalink

I would even recommend 5 minutes as scanning interval. Over 100 Vmware sensors can unfortunately already be a too high load for the SOAP-Connection(s) from the PRTG Probe to the Vmware-system(s). Therefore, remote probes can already help with these amounts of Vmware sensors.


Jul, 2011 - Permalink