VMware probe reports Self-monitoring failures for Provisioned Space in some Data Stores.

Document ID : KB000008366
Last Modified Date : 20/06/2018
Show Technical Document Details

vmware probe Self-Monitoring alarms are created for some data stores.

Self-Monitoring Failures for '<***.<data store>.ProvisionedSpace'. Data Collection (* of * failed).


Other data stores on the same vCenter and being monitored by the same probe report the data as expected.

UIM 8.51vmware probe 8.63

You might see similar error messages in the vmware probe log as follows:

[Data Collector - ****, vmware] Failed to collect data for monitor '***.Provisioned Space'. Updated value will not be available.: Lookup failed for value of monitor '"***:<data store name or ID>"."ProvisionedSpace"'. GUI will not display current value or severity. Will try again next polling cycle.


The vmware probe uses the below formula to calculate the Provisioned Space:

capacity - freeSpace + uncommitted


If any of these values is invalid or not returned to the probe then you might see the Self-Monitoring alarms.

An example of invalid value is when 'uncommitted' returns 'unset' instead of a number.


If you are unable to determine the root cause of the missing/invalid data on your VMware system you can disable the Self-Monitoring alarms or change their severity.

See KB000010371 for instructions.

Additional Information:

You can use the VMware Managed Object Browser (MOB) to check the values in the system. See KB000074904 or consult third party documentation for reference.