vSphere Pod Alert Definitions

The vCenter adapter provides alert definitions that generate alerts on the vSphere Pod objects in your environment.

Health/Symptom-Based

These alert definitions have the following impact and criticality information.

Impact

Risk/Health

Criticality

Symptom-based

Alert Definition	Symptoms	Recommendations
Not enough resources for vSphere HA to start the Pod	Not enough resources for vSphere HA to start Pod
One or more Pod guest file systems are running out of disk space	Symptom set is met when any of the symptoms are true: Guest file system space usage at warning level Guest file system space usage at critical level
Pod CPU usage is at 100% for an extended period of time	Pod sustained CPU usage is 100%
Pod disk I/O read latency is high	Symptom set is met when any of the symptoms are true: Pod disk read latency at Warning level Pod disk read latency at Immediate level Pod disk read latency at Critical level
Pod disk I/O write latency is high	Symptom set is met when any of the symptoms are true: Pod disk write latency at Warning level Pod disk write latency at Immediate level Pod disk write latency at Critical level
Pod has CPU contention due to long wait for I/O events	Symptom set is met when any of the symptoms are true: Pod CPU I/O wait is at Critical level Pod CPU I/O wait is at Immediate level Pod CPU I/O wait is at Warning level
Pod has CPU contention due to memory page swapping in the host	Symptom set is met when any of the symptoms are true. Pod CPU swap wait is at Critical level Pod CPU swap wait is at Immediate level Pod CPU swap wait is at Warning level
Pod has CPU contention due to multi-vCPU scheduling issues (co-stop) caused by too many vCPUs	Alert is triggered when all of the symptom sets are true. Pod is powered off Symptom set is met when any of the symptoms are true. Pod CPU co-stop is at Critical level Pod CPU co-stop is at Immediate level Pod CPU co-stop is at Warning level
Pod has memory contention caused by swap wait and high disk read latency	Alert is triggered when all of the symptom sets are true. Symptom set is met when any of the symptoms are true. Pod CPU swap wait is at Warning level Pod CPU swap wait is at Immediate level Pod CPU swap wait is at Critical level Symptom set is met when all of the symptoms are true. Pod disk read latency at Warning level VMware Tools is running Pod does not have memory ballooning
Pod has memory contention due to memory compression, ballooning, or swapping	Alert is triggered when all of the symptom sets are true: Pod memory limit is set Symptom set is met when any of the symptoms are true. Pod memory contention is at Critical level Pod memory contention is at Immediate level Pod memory contention is at warning level Pod memory is compressed Pod memory ballooning is at Warning level Pod memory ballooning is at Immediate level Pod memory ballooning is at Critical level Pod is using swap
Pod is demanding more CPU than the configured limit	Symptom set is met when all of the symptoms are true. Pod CPU limit is set CPU Demand is greater than configured limit
Pod is experiencing memory compression, ballooning, or swapping due to memory limit	Alert is triggered when all of the symptom sets are true. Pod memory limit is set Pod memory demand exceeds configured memory limit Symptom set is met whenanyof the symptoms are true. Pod memory is compressed Pod memory ballooning is at Warning level Pod memory ballooning is at Immediate level Pod memory ballooning is at Critical level Pod is using swap
Pod is in an invalid or orphaned state	Symptom set is met when any of the symptoms are true. Pod is in invalid state Pod is orphaned
Pod on a host with BIOS power management not set to OS controlled is facing CPU contention	Alert is triggered when all of the symptom sets are true: Pod CPU contention at critical level Symptom set is true when all of parent host system exhibit the following symptom. Host power management technology is not set to OS Controlled
Pod on a host with BIOS power management not set to OS controlled is facing CPU contention	Alert is triggered when all of the symptom sets are true. Symptom set is met when all of the symptoms are true. Pod CPU contention is elevated Pod CPU contention at critical level Symptom set is true whenallof parent host system exhibit the following symptom. Host power management technology is not set to OS Controlled
Pod on a host with BIOS power management set to OS controlled is facing CPU contention	Alert is triggered when all of the symptom sets are true. Symptom set is met when all of the symptoms are true. Pod CPU contention is elevated Pod CPU contention is elevated Symptom set is true when all of parent host system exhibit the following symptom. Host power management technology is not set to OS Controlled
Pod on a host with BIOS power management set to OS controlled is facing CPU contention	Alert is triggered when all of the symptom sets are true. Symptom set is met when any of the symptoms are true. Pod CPU contention is elevated Pod CPU contention is elevated Pod CPU contention at critical level Symptom set is true when all of parent host system exhibit the following symptom. Host power management technology is not set to OS Controlled
vSphere HA failed to restart a network isolated Pod	vSphere HA failed to restart a network isolated Pod