-
Título
How to decipher an alarm generated by VMW ESX Server Total Latency rule -
Descrição
How to decipher an alarm generated by VMW ESX Server Total Latency rule
-
Causa
Primary cause is either slower Disk drives or an issue with the storage
-
Resolução
In order to assess where the problem is taking place you should go to the vmExplorer dashboard for the ESX Host that triggered the rule. On this dashboard there is a tab for Storage information. In the table of physical disks you will need to look at the row for the disk that caused the rule to fire and then look at the values for Kernel and Device latency.
-
Informações adicionais
When this rules fires it is due to an ESX server experiencing higher than expected latencies in performing I/O requests on the disks it is attached to. The latencies can happen in two areas:
Kernel: The time spent between the guest OS and the device.
Device: The time spent on the physical device. In VMware's words, "from the HBA to the platter."
The total latency that the rule assesses is the combined read and write latencies for both kernel and device.