Badge Health alert does not become inactive even related alert has been resolved

Products

• VCF Operations

Issue/Introduction

• An alert is triggered which uses the metric 'Badge|Health(%)'.
• However the alert will not become inactive after related alert has been resolved.
• The alert will generate again even through cancel it manually. 
  
  For example:
  
  An alert (alert-1) of ESXi host CPU usage is triggered with the type of Health Critical. Then the metric of 'Badge|Health(%)' will be marked as 25 (Red).
  The alert (alert-2) based on the metric will be triggered too. 
  After ESXi host CPU usage is going down, the alert-1 becomes inactive. However the alert-2 still keeps on Active. 

Environment

VMware Aria Operations 8.18.x

Cause

Badge Health is determined by the most severe Health Alert against an object. The most critical health alert against an object defines that objects badge health. The Criticalities map as follows:

• Critical = Badge Health 25% (red)
• Immediate = Badge Health 50% (orange)
• Warning = Badge Health 75% (yellow)
• Info = Badge Health 100% (green).  

In this scenario the metric 'Badge|Health(%)' still keeps the same value to trigger the alert in loop.

Resolution

To workaround the issue, activate cycle the alert in Policy:

1. Deactivate the alert in policy. See Deactivating Alerts in VMware Aria Operations
2. Wait for a moment to let the alert become inactive on object.
3. Activate the alert in policy again. See Activating the Deactivated Alerts