Hello wsanders11,
Restarting that service may be allowing retrieval of information that was not being communicated until now (potential cause of alerts).
I think it is necessary to establish whether there is a vSAN-cluster issue or a vCenter-to-host communication issue:
check cluster membership that all nodes are participating in cluster:
# esxcli vsan cluster get
Check the reported decom state for all nodes (from any host):
#cmmds-tool find -t NODE_DECOM_STATE -f json
Check clomd service is running on all hosts (should not be running on Witness if stretched-cluster)
# /etc/init.d/clomd status
Are the alarms you are seeing for the node that was disconnected from vCenter or another node?
Bob