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.
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:
|
|
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 I/O write latency is high | Symptom set is met when any of the symptoms are true:
|
|
Pod has CPU contention due to long wait for I/O events | Symptom set is met when any of the symptoms are true:
|
|
Pod has CPU contention due to memory page swapping in the host | Symptom set is met when any of the symptoms are true.
|
|
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.
Symptom set is met when any of the symptoms are true.
|
|
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.
Symptom set is met when all of the symptoms are true.
|
|
Pod has memory contention due to memory compression, ballooning, or swapping |
Alert is triggered when all of the symptom sets are true:
Symptom set is met when any of the symptoms are true.
|
|
Pod is demanding more CPU than the configured limit | Symptom set is met when all of the symptoms are true.
|
|
Pod is experiencing memory compression, ballooning, or swapping due to memory limit |
Alert is triggered when all of the symptom sets are true.
Symptom set is met whenanyof the symptoms are true.
|
|
Pod is in an invalid or orphaned state | Symptom set is met when any of the symptoms are true.
|
|
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 true when all of parent host system exhibit the following symptom.
|
|
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.
Symptom set is true whenallof parent host system exhibit the following symptom.
|
|
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.
Symptom set is true when all of parent host system exhibit the following symptom.
|
|
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.
Symptom set is true when all of parent host system exhibit the following symptom.
|
|
vSphere HA failed to restart a network isolated Pod | vSphere HA failed to restart a network isolated Pod |