CPU Threshold alerts generated for VMware Cloud on AWS environments are not including the SDDC name in the alert payload in VCF Operations for Networks

Products

• VCF Operations for Networks

Issue/Introduction

Currently, the alert only contains the TNT ID (tenant identifier). However, TNT IDs are not unique per SDDC and can exist across multiple SDDCs within the same organization. As a result:

• Multiple SDDCs may share the same TNT number
• Alerts become indistinguishable from each other
• Which SDDC triggered the alert cannot be determined
• This affects triage, routing, automation, and event correlation

Environment

VCF Operations for Networks 6.14.1

Cause

The product is operating as designed. The current alert payload architecture does not append the logical SDDC name to physical host or edge node threshold alerts.

Because a single organization structure can contain multiple SDDCs, the organizational-level TNT ID cannot uniquely identify the specific SDDC originating the alert.

 

Resolution

The following are some workaround suggestions:

1. Entity Cross-Referencing: Extract the specific entity identifier (e.g., Hostname, Edge Node ID, or IP address) from the alert payload.
   
   
2. vRNI Global Search: Input the extracted entity identifier into the VCF Operations for Networks global search. The resulting entity dashboard will explicitly display the parent SDDC and cluster relationship.
   
   
3. Infrastructure Monitoring Pivot: For reliable SDDC-level infrastructure alerting, utilize VCF Operations (formerly vRealize Operations). VCF Operations natively maps the VMC hierarchy and includes the SDDC context directly in alert payloads.  (NOTE:  VCF Operations is a completely separate product than VCF Operations for Networks).
   
   

In parallel, please consider submitting a Feature Request to have the SDDC name appended to the alert payload. Follow the procedure outlined in KB KB 379107 - Submit a VMware by Broadcom feature request