When a vSAN host detects that a device has suspended I/Os, an event is reported in the /var/run/log/vobd.log:
--/var/run/log/vobd.log
YYYY-MM-DDTHH:MM:SS In(14) vobd[#######]: [vSANCorrelator] #######us: [esx.problem.vob.vsan.lsom.stuckiotimeout] vSAN device ########-####-####-####-############ detected I/O timeout error. This may lead to stuck I/O.YYYY-MM-DDTHH:MM:SS In(14) vobd[#######]: [vSANCorrelator] #######us: [esx.problem.vob.vsan.lsom.stuckiooffline] vSAN device ########-####-####-####-############ detected stuck I/O error. Marking the device as offline.
vSAN 8.x
If it's plan to monitor this event with vCenter alarm, it could be added by manually.
Follow the steps mentioned below to set the alarm manually:
Navigate to vCenter Server -> Configure -> Alarm Definitions
Click Add
Input alarm name "vSAN device detected suspended I/Os".
Choose the "Target type" as Hosts and click Next
In the "Alarm Rule1" page, Input "esx.problem.vob.vsan.lsom.stuckiotimeout" as the trigger condition.
Select severity as "Show as Warning"
Optionally, the Send email notifications or Send SNMP traps or Run script could be enabled.
Click Next
In the Review page, verify if the alarm rules is set correctly and make sure the "Enable this alarm" option is enabled.
Click CREATE.
It's suggest to refer follow KB to handle the issue of vSAN stuck I/O.
How to handle lost or stuck I/O on a host in vSAN cluster
https://knowledge.broadcom.com/external/article/326885/