Objects are incorrectly assigned based on the configured policy assignments in Aria Operations.

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

VM is currently assigned to two different policies. Instead of applying the intended default policy, the system applies the higher-priority policy (Policy B). This affects the visibility of certain metrics and super metrics that are tied to the default policy (Policy A).

When metrics are enabled under Policy A, they do not appear for the VM. However, disabling those metrics in Policy A and enabling them in Policy B makes them visible. This occurs because the VM belongs to two custom groups, each mapped to a different policy, and the current policy priority configuration gives precedence to Policy B.

Environment

Aria Operations 8.18.x

Cause

• This is expected behavior, as it occurs due to the correct application of the policy priority logic.

Resolution

In Aria Operations, each object is assigned to a policy, and policies have a priority rating to resolve conflicts.

When an object is associated with multiple policies, the one with the highest priority takes precedence.

To address this, there are two available options:

• Change the policy priority https://techdocs.broadcom.com/us/en/vmware-cis/aria/aria-operations/8-18/vmware-aria-operations-configuration-guide-8-18/configuring-policies/managing-and-administering-policies.html

• Enable the required metric in both policies https://techdocs.broadcom.com/us/en/vmware-cis/aria/aria-operations/8-16/vmware-aria-operations-configuration-guide-8-16/configuring-policies/using-the-monitoring-policy-workspace/policy-workspace/policy-workspace-collect-metrics-and-properties.html

However, due to the your current environment constraints, if neither of these options can be implemented, we have raised a feature request to include the above capability in Aria Operations.

Additional Information

Please find the feature request below