Custom Configured Task Event Alarms Stop Working After Upgrading to vCenter Server 8.x
Article ID: 447269
Updated On:
Products
Issue/Introduction
After upgrading to VMware vCenter Server (vCenter) 8.x, previously configured custom alarms based on task events (e.g., VmSnapshotCreatedEvent or snapshot revert events) stop functioning. Additionally, administrators are unable to edit existing custom alarm definitions or create new ones by pasting the event ID directly into the vSphere Client UI. The user interface returns a "No items to display" warning and rejects the custom event token.
Environment
VMware vCenter Server 8.x
Cause
The vSphere Client UI was explicitly security hardened in vCenter Server 8.x to prevent pasting arbitrary text strings into custom alarm definitions. This strict input validation restriction was implemented to prevent potential malicious code execution and mitigate injection vulnerabilities.
Unlike older vSphere versions, vCenter Server 8.0 does not use specific event types for successful snapshot tasks, but instead marks those tasks as finished with success.
However, vCenter requires an event with a specific event ID to trigger an alarm.
Resolution
Whilst it is currently not natively possible to create an email alarm for when a snapshot task completes successfully, scripting methods using PowerCLI can be used to obtain this information from the environment, For Environmental design architecture and steps for creating polling scripts you may consider VCF Professional Services and Lifecycle Support .
Additionally, you may wish to raise a feature request to formally request native UI functionality for successful snapshot task completion alarms. Submit a VMware by Broadcom feature request
Additional Information
Feedback
