To get vSAN performance graphs/charts, first, you need to enable the vSAN performance service.
Before you configure the vSAN Performance Service, make sure that the cluster is properly configured and has no unresolved health problems.
Configure vSAN Performance ServiceExample:
![image.png](https://api-broadcomcms-software.wolkenservicedesk.com/attachment/get_attachment_content?uniqueFileId=1512264279683)
After the service starts/restarts, go back to the vCenter web Client and click the “Edit” button for the Performance Service box
- Select the appropriate storage policy from the dropdown, ensure the “Turn ON Virtual SAN performance service” box is checked, and click “OK”
![image.png](https://api-broadcomcms-software.wolkenservicedesk.com/attachment/get_attachment_content?uniqueFileId=1512262360682)
- Confirm that the performance service is turned on and reporting healthy
- Ensure all VMs are compliant with the related VM Storage policy.
- Reapply storage policy to VMs if necessary.
- Run the performance health check test again.
Workaround:
1) Restarting the vsanmgmtd service on all the ESXi hosts in the vSAN Cluster. There is no impact of restarting this service on the ESXi hosts,
- /etc/init.d/vsanmgmtd restart
Make sure the service is running after the restart,
- /etc/init.d/vsanmgmtd status
If this doesn't resolve the issue then (provided you don't mind losing historical performance data) consider disabling and re-enabling the performance service which also creates a new stats Object.
2) Re-enable the performance service from the cluster level
- Go to vSAN Cluster > Configure > vSAN > Services
- Click “Turn off” in the “Performance Service”
- Ensure that the Performance Service is disabled by refreshing the page.
- Re-enable the Performance Service and retest the Skyline Health.
3) Check vCenter/ESXi versions, if the vCenter version is on a lower version of ESXi then upgrade vCenter to be equal to or newer than ESXi.
4) Check firewalls and make sure port 80 is not being blocked
5) If the first 4 options don't resolve the issue collect entire cluster logs, open a case with vSAN support, and upload the logs for further investigation.