Looking at the below and with no real data it may be a problem with your vcenter and not vrops as the bottom alert is
"vSAN adapter instance failed to collect data from vSAN Health Service. vSAN Health Service might have issues"
this would point me to a vcenter problem not a vsan adapter problem in vrops.
The vsan health service is a vcenter service. If it cant collect from the vsan health service it would point me to check that the vCenter its self is fully functional first before i start blaming vrops.
If it was me i would be in the vcenter vami checking the health of all my services first