List of deprecated alerts and their associated new alerts in Aria Operations 8.18
Article ID: 375068
Updated On:
Products
Issue/Introduction
When you log into Aria Operations 8.18 you see the following message: "Many out-of-the-box alerts have been deprecated. As a result, you may see alerts with a (DEP) prefix. Deprecated alerts have been replaced by a combination of new alerts and proactive dashboards such as vSphere Daily Check and Live! vSphere Cluster Performance. Deprecated alerts are still enabled in this version for comparison, but they will not be enabled by default in future versions."
Resolution
Here is the list of deprecated alerts and their associated new alerts:
- Business Application: 3 alerts have been deprecated.
Replacement Alerts: None - Tier: 3 alerts have been deprecated.
Replacement Alerts: None - vSphere Cluster: 10 alerts have been deprecated.
Replacement Alerts:
vSphere Cluster has CPU contention
vSphere Cluster has memory contention
vSphere Cluster CPU utilization has reached a critical level
vSphere Cluster memory utilization has reached a critical level -
ESXi Hosts: 3 alerts have been deprecated.
Replacement Alerts:
ESXi has CPU contention
ESXi has memory contention
ESXi host CPU utilization has reached a critical level
ESXi host memory utilization has reached a critical level - Datastore: 2 alerts have been deprecated.
Replacement Alerts: None
Note: There is a mistake in the description as there is no replacement. Deprecated as it could misfire when VM virtual disks are not on the datastore. The metric used are generic at VM level, as opposed to specific virtual disk that resides on the datastore.
If you need alert at this level, a possible workaround is to use datastore level metric. Take note it’s average of all its VMs. - Virtual Machine: 20 Alerts have been deprecated.
Replacement Alert: VM experiencing CPU contention.
Replacement Alert: VM CPU utilization has reached a critical level
Replacement Alert: VM experiencing memory contention
Replacement Alerts:
VM experiencing disk read latency
VM experiencing disk write latency
Replacement Alert: None. This is covered by daily check dashboard. Note: there is a bug in the description. Ignore the text Use the new alert "VM has been running on snapshots for days" as there is no such alert. - Pod: 14 Alerts have been deprecated.
Additional Information
Summary:
(DEP) Virtual machine is demanding more CPU than the configured limit
(DEP) Virtual machine is running on snapshots for more than 2 days
(DEP) Virtual Machine on a host with BIOS power management not set to OS controlled is facing CPU contention
(DEP) Virtual machine in a cluster is demanding more CPU than its entitlement
(DEP) Virtual machine has CPU contention due to multi-vCPU scheduling issues (co-stop) caused by too many vCPUs
(DEP) Virtual machine has memory contention due to memory compression, ballooning, or swapping
(DEP) Virtual machine is experiencing memory compression, ballooning, or swapping due to memory limit
(DEP) Virtual Machine on a host with BIOS power management not set to OS controlled is facing CPU contention
(DEP) Virtual machine has disk I/O latency problem caused by snapshots
(DEP) Virtual machine has CPU contention due to multi-vCPU scheduling issues (co-stop) caused by snapshots
(DEP) Virtual Machine on a host with BIOS power management set to OS controlled is facing CPU contention
(DEP) Virtual machine has memory contention caused by swap wait and high disk read latency
(DEP) Virtual machine is demanding more CPU than its entitlement
(DEP) Virtual machine in a DRS cluster is demanding more CPU than its entitlement
(DEP) Virtual Machine on a host with BIOS power management set to OS controlled is facing CPU contention
(DEP) Fully-automated DRS-enabled cluster has memory contention caused by more than half of the virtual machines
(DEP) Tier Health is degraded
(DEP) Pod on a host with BIOS power management not set to OS controlled is facing CPU contention
(DEP) Standalone host has memory contention caused by overpopulation of virtual machines
(DEP) Pod has CPU contention due to memory page swapping in the host
(DEP) Host in a cluster that does not have fully-automated DRS enabled has CPU contention caused by more than half of the virtual machines
(DEP) Fully-automated DRS-enabled cluster has CPU contention caused by overpopulation of virtual machines
(DEP) Fully-automated DRS-enabled cluster has high CPU workload
(DEP) More than 5% of virtual machines in the cluster have memory contention due to memory compression, ballooning, or swapping
(DEP) Pod has CPU contention due to long wait for I/O events
(DEP) Pod has memory contention due to memory compression, ballooning, or swapping
(DEP) Standalone host has CPU contention caused by more than half of the virtual machines
(DEP) Tier Risk is elevated
(DEP) Fully-automated DRS-enabled cluster has memory contention caused by overpopulation of virtual machines
(DEP) Tier Efficiency is degraded
(DEP) Host is experiencing high number of packets dropped
(DEP) Pod on a host with BIOS power management not set to OS controlled is facing CPU contention
(DEP) Pod on a host with BIOS power management set to OS controlled is facing CPU contention
(DEP) Pod has memory contention caused by swap wait and high disk read latency
(DEP) Fully-automated DRS-enabled cluster has high memory workload and contention
(DEP) Fully-automated DRS-enabled cluster has CPU contention caused by less than half of the virtual machines
(DEP) Virtual machine disk I/O write latency is high
(DEP) Virtual machine disk I/O read latency is high
(DEP) Host in a cluster that does not have fully-automated DRS enabled has CPU contention caused by overpopulation of virtual machines
(DEP) Host in a cluster that does not have fully-automated DRS enabled has memory contention caused by overpopulation of virtual machines
(DEP) Host in a cluster that does not have fully-automated DRS enabled has memory contention caused by less than half of the virtual machines
(DEP) Standalone host has memory contention caused by more than half of the virtual machines
(DEP) Virtual machine has CPU contention due to memory page swapping in the host
(DEP) Host in a cluster that does not have fully-automated DRS enabled has CPU contention caused by less than half of the virtual machines
(DEP) Application Risk is elevated
(DEP) Virtual machine has CPU contention due to long wait for I/O events
(DEP) Standalone host has memory contention caused by less than half of the virtual machines
(DEP) Fully-automated DRS-enabled cluster has CPU contention caused by more than half of the virtual machines
(DEP) Pod on a host with BIOS power management set to OS controlled is facing CPU contention
(DEP) More than half of the virtual machines served by this datastore are facing disk write latency
(DEP) Virtual machine CPU usage is at 100% for an extended period of time
(DEP) Application Health is degraded
(DEP) Application Efficiency is degraded
(DEP) Pod is experiencing memory compression, ballooning, or swapping due to memory limit
(DEP) Pod has CPU contention due to multi-vCPU scheduling issues (co-stop) caused by too many vCPUs
(DEP) Fully-automated DRS-enabled cluster has memory contention caused by less than half of the virtual machines
(DEP) More than half of the virtual machines served by this datastore are facing disk read latency
(DEP) Standalone host has CPU contention caused by overpopulation of virtual machines
(DEP) Pod disk I/O read latency is high
(DEP) Cluster has unbalanced workload
(DEP) Pod is demanding more CPU than the configured limit
(DEP) Standalone host has CPU contention caused by less than half of the virtual machines
(DEP) Pod CPU usage is at 100% for an extended period of time
(DEP) Host in a cluster that does not have fully-automated DRS enabled has memory contention caused by more than half of the virtual machines
(DEP) Pod disk I/O write latency is high
Feedback
