Case scenario:
1. As an example, an alert definition is cloned from "ESXi Host is violating VMware vSphere Security Configuration Guide for vCenter version 8 and above". The cloned alert in this example begins with "GR":
2. This cloned alert is then applied to one or more default or custom policies.
3. This cloned alert's settings are the same as the OOTB, nothing has been changed/customized.
4. In the process of customizing the Compliance Benchmark, the above 2 alerts are selected, and all policies in step 2 are applied.
5. As soon as the custom benchmark is finished, we can see both alerts showing on the benchmark dashboard. The OOTB alert is triggered on 200+ hosts across all policies, which is working as expected. However, the cloned alert is only triggered on 55 hosts that are under one of the policies.
Aria Operations 8.18.x
There is an issue with the cloned compliance alert is not activated under certain policies, although it shows it's activated in the UI.
This issue is currently under review.
Workaround:
1. Instead of cloning the alert, create/add a new identical one manually.
2. Change the name for clearness to differentiate it from cloned and original ones.
3. Make sure the alert is activated in the policies.
4. Proceed with the steps of the Custom Benchmark and select the newly created alert.