# Data Object - VsanClusterHealthQuerySpec(vim.cluster.VsanClusterHealthQuerySpec)

Parameter to
  VsanQueryVcClusterHealthSummary
Extends
  DynamicData
See also
  Task
Since
  vSAN API vSAN 7.0U1

## Data Object Description

Properties

Name | Type | Description
--- | --- | ---
diskNames* | xsd:string[] | A list of disks to be validated for hardware compatibility. If this field is set, the hardware compatibility check will only return the result of the disks in list. Both disk canonical name (e.g. 'mpx.vmhba0:C0:T0:L0') and UUID are supported. The field only takes effect with perspective 'vcsaInstallerForVsanEsa'. Since vSAN API 8.0.0.1
includeHealthRemediation* | xsd:boolean | True to include vSAN health remediation and troublehshooting information in the data driven health test result. It's false by default or when it's not set. Since vSAN API 8.0.0.2
task* | ManagedObjectReference to a Task | Task ID returned from API vim.cluster.VsanVcClusterHealthSystem#QueryClusterHealthSummaryTask. This is used to get the health summary performed by the given task. If the task is still runing, vim.cluster.VsanVcClusterHealthSystem#QueryClusterHealthSummary returns health check groups which are already completed. If the task is completed, vim.cluster.VsanVcClusterHealthSystem#QueryClusterHealthSummary returns full health summary from cache (Notes: fetchFromCache should be True). vim.cluster.VsanVcClusterHealthSystem#QueryClusterHealthSummary returns VsanFault if task ID is invalid or task state is 'error'.
Properties inherited from DynamicData
None

*Need not be set
Show WSDL type definition
<complexType xmlns="http://www.w3.org/2001/XMLSchema" xmlns:vsan="urn:vsan" name="VsanClusterHealthQuerySpec"> <complexContent> <extension base="vsan:DynamicData"> <sequence> <element name="task" type="vsan:ManagedObjectReference" minOccurs="0"/> <element name="diskNames" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/> <element name="includeHealthRemediation" type="xsd:boolean" minOccurs="0"/> </sequence> </extension> </complexContent> </complexType>