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

.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

• Knowledge Base: I cannot add VMware sensors because of "wrong" password although it is correct. What can I do?
• Knowledge Base: Why are my VMware sensors not working after upgrading to VCSA 6.5 U1?

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:

• Discard result (default): Do not store the sensor result.
• Store result: Store the sensor result and the last response 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.

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:

• 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. 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.

Accessible

The accessibility of the datastore

• Up status: Yes
• Down status: No

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)