Alerts are not triggered from NSX-T notification events

Products

• VMware Aria Suite

Issue/Introduction

When notification events come from the NSX-T integration into Aria Operations, they are dynamic in nature. This means that sometimes when an Event is generated on the NSX-T side, Aria Operations collects this event via API and associates it to an object that has been collected into Aria Operations inventory and other times an object is not able to be associated to the event. It would then be considered a generic INFO level alert. This may prevent user defined alerts or notifications to not trigger if these were defined based on the specific NSX-T object such as a transport node for example.

In the example below, the INFO level notification event comes in, but a defined alert from Aria Operations to trigger a new critical alert or send an email notification may not activate. You can see that the alert basis is tied to the 'NSXTAdapterInstance' instead of an actual object.

 

 

Environment

Aria Operations 8.x

Cause

This is because the events that come from NSX-T are dynamic in nature and is expected behavior at the time of writing. When the event that comes from NSX-T into Aria Operations is not able to be mapped to an object, the alert may be INFO level only and will be mapped to the NSX-T adapter instance name as a default.

Resolution

To workaround this issue, when defining the symptom and alert in Aria Operations, choose the NSX-T adapter instance name as the object type. Then configure the remaining definition as needed such as message text filters to key in on any specific Event you need that gets pulled from NSX-T via API.