VMware Aria Operations report does not display Virtual Machine disk provisioning type (Thin or Thick)

Products

• VCF Operations

Issue/Introduction

In VMware Aria Operations 8.18.x, configuration reports generated for Virtual Machines fail to display the disk provisioning type. The columns or properties related to whether a disk is thin-provisioned or thick-provisioned show up as blank, missing, or unpopulated in the final export or view.

Environment

 

• VMware Aria Operations 8.18.x

• vCenter Server 7.x / 8.x

 

Cause

The metric property tracking disk allocation types (Virtual Disk | Storage Provisioning Type or Disk Space | Provisioning Type) is deactivated by default within the standard monitoring policy to balance performance overhead. Consequently, the vCenter adapter does not collect or persist this information in the Aria database until explicit activation occurs.

Resolution

1. Verify vCenter Collection Account Privileges:

• Ensure that the service account used by Aria Operations to connect to vCenter Server has the Storage views -> View permission enabled globally in vCenter.

• If permissions are missing, update the role in vCenter, then navigate to Aria Operations > Administration > Integrations and manually trigger a test connection for the vCenter adapter instance.

2. Enable Metric/Property Collection in Policy:

 

• Log in to the VMware Aria Operations user interface with administrator privileges.

• Navigate to Configure > Policies from the left-hand navigation pane.

• Select the active policy utilized for the vSphere monitoring environment and click Edit Policy.

• In the policy workspace, navigate to the Metrics and Properties section.

• In the object type filter, select or type Virtual Machine.

• Expand the Properties hierarchy tree, then expand Virtual Disk or Disk Space.

• Locate the specific attribute entry for Storage Provisioning Type or Provisioning Type.

• Change the configuration state under the State column from Inherited (Disabled) or Disabled to Enabled.

• Click Save to preserve policy adjustments.

• Allow a minimum of 2 to 3 successive object collection cycles (approximately 10 to 15 minutes) for the properties to retrieve from <REDACTED_HOSTNAMES> and populate inside reports.