Notification: Many out-of-the-box alerts have been deprecated
search cancel

Notification: Many out-of-the-box alerts have been deprecated

book

Article ID: 375068

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

Logging into Aria Operations displays the 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."


Additional Possible Issue:
If the alerts with (DEP) prefix were adjusted for different symptom thresholds specific to your environment, the replacement alert may cause false positive alerts in email notifications or 3rd party ticketing systems . You will need to adjust the symptom threshold for your environment or deactivate the new alert in the policy if you do not need to be alerted on it.

Environment

Aria Operations 8.18.x

Resolution

Full list of deprecated alerts, separated by object type, and their new replacement alerts

Business Application:

  • Deprecated alerts:

(DEP) Application Risk is elevated
(DEP) Application Health is degraded
(DEP) Application Efficiency is degraded

  • Replacement alerts: None

Tier:

  • Deprecated alerts:

(DEP) Tier Health is degraded
(DEP) Tier Risk is elevated
(DEP) Tier Efficiency is degraded

  • Replacement alerts: None

vSphere Cluster:

  • Deprecated alerts:

(DEP) Fully-automated DRS-enabled cluster has CPU contention caused by overpopulation of virtual machines
(DEP) Fully-automated DRS-enabled cluster has CPU 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) Fully-automated DRS-enabled cluster has high memory workload and contention
(DEP) Fully-automated DRS-enabled cluster has memory contention caused by less than half of the virtual machines
(DEP) Fully-automated DRS-enabled cluster has memory contention caused by more than half of the virtual machines
(DEP) Fully-automated DRS-enabled cluster has memory contention caused by overpopulation of virtual machines
(DEP) Cluster has unbalanced workload
(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

  • 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:

  • Deprecated alerts

(DEP) Standalone host has memory contention caused by overpopulation of virtual machines
(DEP) Standalone host has CPU contention caused by more than half of the virtual machines
(DEP) Standalone host 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) Standalone host has CPU contention caused by overpopulation of virtual machines
(DEP) Standalone host has CPU contention caused by less than half of the 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) 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 CPU contention caused by more than half of the virtual machines
(DEP) Host is experiencing high number of packets dropped
(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) Host in a cluster that does not have fully-automated DRS enabled has memory contention caused by more than half of the virtual machines

  • 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:

  • Deprecated alerts:

(DEP) More than half of the virtual machines served by this datastore are facing disk read latency
(DEP) More than half of the virtual machines served by this datastore are facing disk write latency

  • 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, which is an average of all associated VMs.

Virtual Machine:

  • Deprecated alerts:

(DEP) Virtual machine has CPU contention due to long wait for I/O events
(DEP) Virtual machine has CPU contention due to memory page swapping in the host
(DEP) Virtual machine has CPU contention due to multi-vCPU scheduling issues (co-stop) caused by too many vCPUs
(DEP) Virtual machine has CPU contention due to multi-vCPU scheduling issues (co-stop) caused by snapshots
(DEP) Virtual machine in a cluster is demanding more CPU than its entitlement
(DEP) Virtual machine in a DRS cluster is demanding more CPU than its entitlement
(DEP) Virtual machine is demanding more CPU than its entitlement
(DEP) Virtual machine is demanding more CPU than the configured limit
(DEP) Virtual Machine on a host with BIOS power management not set to OS controlled is facing CPU contention
(DEP) Virtual Machine on a host with BIOS power management not set to OS controlled is facing CPU contention
(DEP) Virtual Machine on a host with BIOS power management set to OS controlled is facing CPU contention
(DEP) Virtual Machine on a host with BIOS power management set to OS controlled is facing CPU contention

  • Replacement alert:

VM experiencing CPU contention.

  • Deprecated alert:

(DEP) Virtual machine CPU usage is at 100% for an extended period of time

  • Replacement alert:

VM CPU utilization has reached a critical level

  • Deprecated alerts:

(DEP) Virtual machine has memory contention due to memory compression, ballooning, or swapping
(DEP) Virtual machine has memory contention caused by swap wait and high disk read latency
(DEP) Virtual machine is experiencing memory compression, ballooning, or swapping due to memory limit

  • Replacement alert:

VM experiencing memory contention

  • Deprecated alerts:

(DEP) Virtual machine has disk I/O latency problem caused by snapshots
(DEP) Virtual machine disk I/O write latency is high
(DEP) Virtual machine disk I/O read latency is high

  • Replacement alerts:

VM experiencing disk read latency
VM experiencing disk write latency

  • Deprecated alert:

(DEP) Virtual machine is running on snapshots for more than 2 days

  • 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:

  • Deprecated alerts:

(DEP) Pod on a host with BIOS power management not set to OS controlled is facing CPU contention
(DEP) Pod has CPU contention due to memory page swapping in the host
(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) 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) Pod on a host with BIOS power management set to OS controlled is facing CPU contention
(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) Pod disk I/O read latency is high
(DEP) Pod is demanding more CPU than the configured limit
(DEP) Pod CPU usage is at 100% for an extended period of time
(DEP) Pod disk I/O write latency is high

  • Replacement alerts: None

Additional Information



 

 



Powered by Wolken Software