Good point. We are working on it. Yet, I don't agree with your take entirely.
MDADM and disks are non-StarWind products. Users are welcome to implement their flavor of third-party monitoring. SNMP or Zabbix are the first solutions that come to my mind; both are third-party solutions.
VSAN logging in its current state is not as bad as it might seem from this thread. True, the logging in its existing form does not indicate a disk or MDADM failure, yet VSAN still will log being unable to write to an *.img, which can be interpreted as an issue with StarWind's underlying storage, and send you an alert. On the other hand, such alerting will be excessive as it does not distinguish between actual disk failure and, say, disk halt due during the VM snapshots (we don't recommend doing snapshots of StarWind VMs or backing them up; see
https://www.starwindsoftware.com/best-p ... practices/).
Speaking of precise disk monitoring, Disk monitoring is available for systems with ProActive Support (i.e., vHCA, HCA, and ProActive support).
Still, we are working on convenient MDADM monitoring for all users since the product is coming as an appliance.