The VMware Host Performance (SOAP) sensor monitors a VMware host server using the Simple Object Access Protocol (SOAP).
VMware Host Performance (SOAP) Sensor
For 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)
Remarks
This sensor has a very high performance impact. We recommend that you use no more than 50 of this sensor on each probe.
This sensor requires.NET 4.7.2 or later from Microsoft on the probe system.
We recommend Windows Server 2012 R2 on the probe system for best performance of this sensor.
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).
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.
If the name contains angle brackets (<>), PRTG replaces them with braces ({}) for security reasons. For more information, see the Knowledge Base: What security features does PRTG include?
This setting is for your information only. You cannot change it.
Tags
Enter one or more tags. Confirm each tag with the Spacebar key, a comma, or the Enter key. You can use tags to group objects and use tag-filtered views later on. Tags are not case-sensitive. Tags are automatically inherited.
It is not possible to enter tags with a leading plus (+) or minus (-) sign, nor tags with parentheses (()) or angle brackets (<>).
For performance reasons, it can take some minutes until you can filter for new tags that you added.
The sensor has the following default tags that are automatically predefined in the sensor's settings when you add the sensor:
esxserverhostsensor
Priority
Select a priority for the sensor. This setting determines the position of the sensor in lists. The highest priority is at the top of a list. Choose from the lowest priority () to the highest priority ().
VMware Host Settings
VMware Host Settings
Setting
Description
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: 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.
This option is not available when the sensor runs on the hosted probe of a PRTG Hosted Monitor instance.
In a cluster, PRTG stores the result in the PRTG data directory of the master node.
Sensor Display
Sensor Display
Setting
Description
Primary Channel
Select a channel from the list to define it as the primary channel. In the device tree, the last value of the primary channel is always displayed below the sensor's name. The available options depend on what channels are available for this sensor.
You can set a different primary channel later by clicking below a channel gauge on the sensor's Overview tab.
Graph Type
Define how different channels are shown for this sensor:
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. You 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. All channels with this unit are stacked 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 under the corresponding setting name to disable the inheritance and to display its options.
For more information, see section Root Group Settings, section Scanning Interval.
Schedules, Dependencies, and Maintenance Window
You cannot interrupt the inheritance for schedules, dependencies, and maintenance windows. The corresponding settings from the parent objects are always active. However, you can define additional schedules, dependencies, and maintenance windows. They are active at the same time as the parent objects' settings.
Schedules, Dependencies, and Maintenance Window
For more information, see section Root Group Settings, section Schedules, Dependencies, and Maintenance Window.
Access Rights
Access Rights
For more information, see section Root Group Settings, section Access Rights.
Channel Unit Configuration
Which channel units are available depends on the sensor type and the available parameters. If no configurable channels are available, this field shows No configurable channels.
Channel Unit Configuration
For more information, see section Root Group Settings, section Channel Unit Configuration.
Channel List
Which channels the sensor actually shows might depend on the target device, the available components, and the sensor setup.
Channel
Description
CPU Ready (Percent)
The CPU readiness (%)
CPU Usage
The CPU usage
This 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
Disk.DeviceLatency
The disk device latency
Disk.KernelLatency
The disk kernel latency
Downtime
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
Power
The average host power usage
More
KNOWLEDGE BASE
I cannot add VMware sensors because of "wrong" password although it is correct. What can I do?