Alerts occur in two ways, based on the health score and the alert forwarding mechanism from the NSX Advanced Load Balancer.
- Based on the health score
Alerts are triggered for virtual services and service engines based on the health score, using the same color code used in the NSX Advanced Load Balancer. The default Wait/Cancel cycle is set to 1. Alerts are grouped as following:
- Critical, when the total health score is less than 70.
- Warning, when the health score is between 70 and 89.
- Alert forwarding from the NSX Advanced Load Balancer
The management pack has an alert forwarding mechanism that mirrors the alerts and sends them from the NSX Advanced Load Balancer to vRealize Operations.
Any new alert generated in the NSX Advanced Load Balancer instance, after the previous collection cycle, is forwarded to the corresponding object in vRealize Operations as a "Notification Event". If the same alert does not recur in the next collection cycle, then it is assumed that the alert has been canceled. Alerts are grouped into Critical, Warning, and Info, corresponding to the alert levels from the NSX Advanced Load Balancer which are "ALERT_HIGH", "ALERT_MEDIUM", "ALERT_LOW.
These alerts are currently not supported on the Management Controller and Controller objects because of an ambiguity while mapping alerts to these two objects.
