<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> PRTG Manual: VMware Host Performance (SOAP) Sensor

The VMware Host Performance (SOAP) sensor monitors a VMware host server using the Simple Object Access Protocol (SOAP).

VMware Host Performance (SOAP) Sensor

VMware Host Performance (SOAP) Sensor

i_square_cyanFor a detailed list and descriptions of the channels that this sensor can show, see section Channel List.

Sensor in Other Languages

  • Dutch: VMware Host Prestaties (SOAP)
  • French: VMware performances du serveur hôte (SOAP)
  • German: VMware Hostserver Leistung (SOAP)
  • Japanese: VMware ホストパフォーマンス(SOAP)
  • Portuguese: Performance do host VMware (SOAP)
  • Russian: Работа узла VMware (SOAP)
  • Simplified Chinese: VMware 主机性能 (SOAP)
  • Spanish: Rendimiento de host VMware (SOAP)


Consider the following remarks and requirements for this sensor:



Performance impact

  • This sensor has a very high performance impact. We recommend that you use no more than 50 of this sensor on each probe.

.NET 4.7.2 or later

  • This sensor requires .NET 4.7.2 or later from Microsoft on the probe system. In a cluster, install it on every cluster node.

i_round_redIf the framework is missing, you cannot create this sensor.

i_square_cyanFor more information, see the Knowledge Base: Which .NET version does PRTG require?

Windows Server

  • We recommend Windows Server 2016 on the probe system for best performance of this sensor.

Parent device

  • This sensor requires that the parent device is a VMware ESXi server as of version 5.2. We recommend that you do not use this sensor on your vCenter. Reliable hardware information can only be provided when this sensor is created on your physical host server as parent device.


  • This sensor requires credentials for VMware/XenServer in the settings of the parent device. Enter a user with sufficient access rights to obtain statistics (read-only usually works).


  • This sensor supports IPv6.

Knowledge Base

Settings on VMware Host System

If you set up this sensor on different probes (for example, when using remote probes or when running a failover cluster), you might need to change the settings of your VMware host so that it accepts more incoming connections. Otherwise, you might get connection timeouts when running plenty of VMware sensors with a short scanning interval.

i_square_cyanFor more information, see the Knowledge Base: How can I increase the connection limit on VMware systems? PE121.

Basic Sensor Settings

Basic Sensor Settings

Basic Sensor Settings

The sensor has the following default tags that are automatically predefined in the sensor's settings when you add the sensor:

  • esxserverhostsensor

i_square_cyanFor more information about basic sensor settings, see section Sensor Settings.

VMware Host Settings

VMware Host Settings

VMware Host Settings



Managed Object Identifier (MOID)

The managed object identifier of the host that this sensor monitors.

Result Handling

Define what PRTG does with the sensor result:

  • Discard result (default): Do not store the sensor result.
  • Store result: Store the last sensor result in the \Logs\sensors subfolder of the PRTG data directory on the probe system. The file names are Result of Sensor [ID].txt and Result of Sensor [ID].Data.txt. This setting is for debugging purposes. PRTG overwrites these files with each scanning interval.

i_podThis option is not available when the sensor runs on the hosted probe of a PRTG Hosted Monitor instance.

i_round_blueIn a cluster, PRTG stores the result in the PRTG data directory of the master node.

Sensor Display

Sensor Display

Sensor Display



Primary Channel

Select a channel from the list to define it as the primary channel. In the device tree, PRTG displays the last value of the primary channel below the sensor's name. The available options depend on what channels are available for this sensor.

i_round_blueYou can set a different primary channel later by clicking b_channel_primary below a channel gauge on the sensor's Overview tab.

Graph Type

Define how this sensor shows different channels:

  • Show channels independently (default): Show a graph for each channel.
  • Stack channels on top of each other: Stack channels on top of each other to create a multi-channel graph. This generates a graph that visualizes the different components of your total traffic.
    i_round_redYou cannot use this option in combination with manual Vertical Axis Scaling (available in the channel settings).

Stack Unit

This setting is only visible if you select Stack channels on top of each other above.

Select a unit from the list. PRTG stacks all channels with this unit on top of each other. By default, you cannot exclude single channels from stacking if they use the selected unit. However, there is an advanced procedure to do so.

Inherited Settings

By default, all of these settings are inherited from objects that are higher in the hierarchy. We recommend that you change them centrally in the root group settings if necessary. To change a setting for this object only, click b_inherited_enabled under the corresponding setting name to disable the inheritance and to display its options.

i_square_cyanFor more information, see section Inheritance of Settings.

Channel List

i_round_blueWhich channels the sensor actually shows might depend on the target device, the available components, and the sensor setup.



CPU Ready (Percent)

The CPU readiness (%)

CPU Usage

The CPU usage

i_round_blueThis channel is the primary channel by default.

Datastore Total ReadLatency

The datastore total read latency

Datastore Total WriteLatency

The datastore total write latency

Disk Read

The disk read speed

Disk Usage

The disk usage

Disk Write

The disk write speed


The disk device latency


The disk kernel latency


In the channel table on the Overview tab, this channel never shows any values. PRTG uses this channel in graphs and reports to show the amount of time in which the sensor was in the Down status

Memory Active

The active memory

Memory Consumed

The consumed memory

Memory Consumed (Percent)

The memory consumed (%)

Memory Swap Used

The used memory swap

Network Received

The received bytes

Network Transmitted

The transmitted bytes

Network Usage

The total network usage


The average host power usage


i_square_blueKNOWLEDGE BASE

I cannot add VMware sensors because of "wrong" password although it is correct. What can I do?

Why are my VMware sensors not working after upgrading to VCSA 6.5 U1?

Which .NET version does PRTG require?

How can I increase the connection limit on VMware systems? PE121

What security features does PRTG include?

Monitoring VMware ESXi 5.5 does not work. What can I do?

For which sensor types do you recommend at least Windows Server 2016 and why?