E-mail Notifications for specific Alerts Not Received from VMware Aria Operations Despite Successful Outbound Test

Products

• VCF Operations

Issue/Introduction

• Alerts configured to send outbound emails are not being forwarded to the recipient. While the outbound SMTP configuration passes the "Test Connection" and other notification rules function correctly, specific alerts are missing.
  
  
• The Outbound Instance (SMTP) is confirmed as working and validated using following steps :
  1.Navigate to Operations > Configurations > Outbound Settings.
  2.Select the Standard Email Plugin instance you are troubleshooting.
  3.Click the Vertical Ellipsis (⋮) and select Edit.
  4.Click the Test button.
  5. Success: A green checkmark appears. This confirms the plugin instance itself is functional.
  
  
• Performing a Notification Rule "Test Process" Fails. Aria Operations 8.18 includes a "Test Notification" workflow within the rule itself to simulate an alert trigger. It can be validated as follows :

  1.Navigate to Operations > Configurations > Notifications.
  2.Select your Notification Rule and click Edit.
  3.Go to the Test Notification tab.
  4.Click Initiate Process. The system will run a 5-step validation:
  5.Validate Criteria: Checks if the filters are logically sound.
  6.Establish Endpoint Connection: Re-verifies the SMTP link.
  7.Authentication: Validates mail server credentials.
  8.Send Notification: Attempts to push a test payload.
  9.Endpoint Receives Notification: (Manual Verification) Check the recipient's inbox for a "Test Notification" email.

Environment

VMware Aria Operations (formerly vRealize Operations)

Cause

The Notification Rule criteria are misconfigured. Specifically, the Alert Type, Alert Sub-Type, or Object Scope filters do not align with the triggered alert's properties, causing the notification engine to skip the outbound action.

Resolution

To resolve this, the Notification Rule must be adjusted to match the metadata of the alerts you wish to receive.

Part 1: Identifying the Alert Definition, Type, and Object

Before fixing the rule, triggered alert should be identified exactly what the  "looks like" to the system. Check the same as follows: 

1.In the Aria Operations UI, navigate to Alerts > Alerts.
2.Locate an instance of the alert that was triggered but not emailed.
3.Click the Alert Name to open the Alert Details.
4.Under Alert Basis, Identify Object Type: Look at the "Object" field (e.g., Virtual Machine, vSAN Cluster).
5.Identify Alert Type/Sub-type: * Click on the Alert Definition link within the summary.

Under the Summary or Configuration tab of the definition, note the Alert Type (e.g., Virtualization) and Alert Sub-Type (e.g., Availability).

Part 2: Correcting the Notification Rule

1.Navigate to Operations > Configure > Notifications.
2.Select the failing rule and click Edit.
3.Under Step 2: Define Criteria:
4.Ensure the "Object Type" matches the object identified in Part 1. (e.g., If the alert is on a Host, the scope must include Host System).
5.Under Alert Scope : Select set of Alerts you would like to receive notifications about. (e.g. Category, Criticality, and Control state.)
6.Notify On: Select the Alert status change you want to receive notifications on.

Once changes are done, trigger a "Test Notification" within the rule itself, but note that this only tests the plugin. To test the filter, use the "Test Notification" method by lowering an alert threshold on a test object to ensure it meets the Notification Rule criteria.