Unable to reduce Aria Operations alert notification time below 5 minutes
Article ID: 427996
Updated On:
Products
Issue/Introduction
Users may experience a delay in receiving alert notifications for production ESXi hosts within VMware Aria Operations (formerly vRealize Operations). When attempting to configure symptoms or alert definitions for immediate notification, the minimum "Wait Cycle" of 1 still results in a 5-minute delay before the alert is triggered and sent to the notification outbound plugin.
Environment
VMware Aria Operations 8.18.x
Cause
It is not possible to reduce the alert notification time below the collection interval of the associated adapter. By default, the vCenter adapter uses a 5-minute collection interval.
The Wait Cycle setting represents the number of consecutive Collection Cycles a condition must remain true. Even when set to 1, the system must complete the full collection, processing, and analysis loop (5 minutes) before the alert can be state-changed and fired.
Resolution
Aria Operations is a polling-based platform. For "instant" or near real-time alerting on critical production host failures, it is a best practice to use push-based mechanisms rather than polling:
-
Configure SNMP Traps: Configure ESXi hosts to send SNMP traps directly to a Northbound Network Management System (NMS).
-
Aria Operations for Logs: Forward ESXi Syslog to Aria Operations for Logs (formerly vRealize Log Insight). Log-based alerts trigger as soon as the specific log pattern is ingested, bypassing the 5-minute metric collection cycle.
Additional Information
Feedback
