What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags

View all Tags

Probe health and VMware



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?

esx health probe prtg vmware

Created on Jun 30, 2011 11:02:50 AM

4 Replies

Accepted Answer




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.

Created on Jun 30, 2011 6:04:00 PM by  Torsten Lindner [Paessler Support]



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

Created on Jul 1, 2011 7:33:28 AM



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?

Created on Jul 1, 2011 10:16:55 AM



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.

Created on Jul 1, 2011 12:23:26 PM by  Torsten Lindner [Paessler Support]

Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.