PRTG Manual: VMware Datastore (SOAP) Sensor
The VMware Datastore (SOAP) sensor monitors the disk usage of a VMware datastore using the Simple Object Access Protocol (SOAP).
For a detailed list and descriptions of the channels that this sensor can show, see section Channel List.
- Dutch: VMware Datastore (SOAP)
- French: VMware Datastore (SOAP)
- German: VMware Datastore (SOAP)
- Japanese: VMware Datastore(SOAP)
- Portuguese: Armazenamento de dados VMware (SOAP)
- Russian: Хранилище данных VMware (SOAP)
- Simplified Chinese: VMware 数据存储 (SOAP)
- Spanish: Almacén de datos VMware (SOAP)
Consider the following remarks and requirements for this sensor:
Remark |
Description |
---|---|
.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. If the framework is missing, you cannot create this sensor. For 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 or vCenter. |
Credentials |
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). |
IPv6 |
This sensor supports IPv6. |
Performance impact |
This sensor has a very low performance impact. |
Lookups |
This sensor uses lookups to determine the status values of one or more channels. |
Limits |
This sensor has predefined limits for several metrics. |
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.
For more information, see the Knowledge Base: How can I increase the connection limit on VMware systems? PE121.
The sensor has the following default tags that are automatically predefined in the sensor's settings when you add the sensor:
- vmwaredatastoreexternsensor
For more information about basic sensor settings, see section Sensor Settings.
Setting |
Description |
---|---|
Managed Object Identifier (MOID) |
The managed object identifier (MOID) of the datastore that this sensor monitors. |
Result Handling |
Define what PRTG does with the sensor result:
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. |
Setting |
Description |
---|---|
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. You can set a different primary channel later by clicking below a channel gauge on the sensor's Overview tab. |
Graph Type |
Define how this sensor shows different channels:
|
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. |
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 Inheritance of Settings.
Which channels the sensor actually shows might depend on the target device, the available components, and the sensor setup.
Channel |
Description |
---|---|
Accessible |
The accessibility of the datastore
|
Available Capacity |
The available capacity (the physically or virtually available size of the datastore) |
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 |
Free Bytes |
The free space (the disk space that is not used by VMs. Used disk space can be either thick-provisioned or used by thin-provisioned virtual disks) |
Free Space |
The free space (%) (the disk space that is not used by VMs. Used disk space can be either thick-provisioned or used by thin-provisioned virtual disks) This channel is the primary channel by default. |
Total Provisioned |
The total provisioned disk space (%) (the sum of all potentially used disk space of thin-provisioned and thick-provisioned VM hard drives, that is, the uncommitted bytes plus used bytes) |
Uncommitted Bytes |
The uncommitted bytes (the disk space that is provisioned for thin-provisioned VMs but not used yet) |
KNOWLEDGE 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?