VsanObjectOverallHealth
The vSAN overall object health includes health status for each of object and the object version compliance status
{
"_typeName": "string",
"objectHealthDetail": [
{
"_typeName": "string",
"numObjects": 0,
"health": "string",
"objUuids": [
"string"
],
"vsanClusterUuid": "string"
}
],
"objectsComplianceDetail": [
{
"_typeName": "string",
"checkTime": "string",
"profile": "string",
"objectUUID": "string",
"complianceStatus": "string",
"mismatch": false,
"violatedPolicies": [
{
"_typeName": "string",
"id": "string",
"expectedValue": "string",
"currentValue": "string"
}
],
"operationalStatus": {
"_typeName": "string",
"healthy": false,
"operationETA": "string",
"operationProgress": 0,
"transitional": false
},
"objPolicyGenerationId": "string"
}
],
"objectVersionCompliance": false,
"objectFormatChangeRequiredUuids": [
"string"
],
"objectsRelayoutBytes": 0,
"globalDedupStoreHealth": "string"
}
The object health list each of which includes the health status, the number of objects on this health status and the object UUID list.
The vSAN objects profile compliance check result
True to indicate all of the objects have compliant object version with the latest supported vSAN disk format.
The latest vSAN disk format version should be version 4 and the vSAN disk upgrade is needed when this flag is false
The vSAN objects which need object layout format change to get capacity improvement
The total bytes for objects need relayout
The global dedup store health that is value of the enum type vim.host.VsanObjectHealthState.
Global dedup store contains some hash objects and chunk objects, and the global dedup store health is an aggregation of each hash and chunk object health. Health will always pick the most serious hash or chunk object health as the global dedup store health.