6.3
Table Of Contents
- vRealize Operations Definitions for Metrics, Properties, and Alerts
- Contents
- About vRealize Operations Manager Reference for Metrics, Properties, and Alerts
- Metric Definitions in vRealize Operations Manager
- Property Definitions in vRealize Operations Manager
- Alert Definitions in vRealize Operations Manager
- Cluster Compute Resource Alert Definitions
- Host System Alert Definitions
- vSphere Distributed Port Group
- Virtual Machine Alert Definitions
- vSphere Distributed Switch Alert Definitions
- vCenter Server Alert Definitions
- Datastore Alert Definitions
- Data Center Alert Definitions
- Custom Data Center Alert Definitions
- Index
Alert Definition Symptoms Recommendations
More than 5% of virtual machines in
the cluster have memory contention
caused by memory compression,
ballooning or swapping.
n
! Virtual machine memory limit is
set AND
n
> 5% of descendant virtual
machines have [ virtual machine
memory contention is at
warning/immediate/critical level]
AND
n
> 5% of descendant virtual
machines have [ Virtual machine
memory is compressed OR
n
Virtual machine is using swap
OR
n
Virtual machine memory
ballooning is at
warning/immediate/critical level]
1 Add more hosts to the cluster to
increase memory capacity.
2 vSphere vMotion some virtual
machines o the host or cluster.
DRS-enabled cluster has unexpected
high memory workload and
contention.
Symptoms include all of the
following:
n
DRS enabled
n
DRS fully automated
n
Cluster memory contention
above DT
n
Cluster memory content is at
warning/immediate/critical level
n
Cluster memory workload at
warning/immediate/critical level
1 Check the applications running on
the virtual machines in the cluster
to determine whether high
memory workload is an expected
behavior.
2 Add more hosts to the cluster to
increase memory capacity.
3 Use vSphere vMotion to migrate
some virtual machines to a
dierent cluster if possible.
vSphere HA failover resources are
insucient.
vSphere HA failover resources are
insucient (fault symptom)
n
Use similar CPU and memory
reservations for all virtual
machines in the cluster OR
n
Use a dierent vSphere HA
admission control policy, such as
reserving a percentage of cluster
resource for failover OR
n
Use advanced options to specify a
cap for the slot size.
For more information, see the vSphere
Availability Guide. Hosts that have
vSphere HA agent errors are not good
candidates for providing failover
capacity in the cluster and their
resources are not considered for
vSphere HA admission control
purposes. If many hosts have a
vSphere HA agent error, the vCenter
Server generates this event leading to
the fault. To resolve vSphere HA agent
errors, check the event logs for the
hosts to determine the cause of the
errors. After you resolve any
conguration problems, recongure
vSphere HA on the aected hosts or on
the cluster
vSphere HA master missing. vCenter Server is unable to nd a
master vSphere HA agent (fault
symptom)
Check the fault page under the
Analysis tab for this object to nd
more objects.
vRealize Operations Definitions for Metrics, Properties, and Alerts
130 VMware, Inc.