When multiple Alert policies are applied to an entity, which will take precedence?

Nutanix Prism Central applies alert policies based on a hierarchy of specificity. When multiple policies are configured for the same alert and could apply to a single entity, the most specific policy takes precedence. A policy applied directly to an individual entity (e.g., a specific VM) is considered the most specific. This overrides policies applied to broader groups, such as a category the entity belongs to, or a general policy applied to all entities of that type (e.g., all VMs).

B. Policy are applied to all entities of an entity type. This is the least specific type of policy and has the lowest precedence. It is overridden by both category-specific and entity-specific policies.

C. Policy are applied to an entity type in a category. This policy is more specific than one applied to all entities of a type, but it is less specific than a policy applied directly to an individual entity.

D. Policy are applied to an entity type in a cluster. This is not a distinct level in the defined precedence hierarchy. A cluster is an entity, so a policy can be applied to a specific cluster, which would fall under the highest precedence rule.

1. Nutanix Prism Central Guide (AOS 6.5)

Section: Alerts and Events Management > Configuring an Alert Policy > Alert Policy Precedence

Content: "When multiple policies apply to an entity, the policy that is most specific to the entity takes precedence. The order of precedence is as follows: 1. A policy applied to a specific entity. 2. A policy applied to entities in a category. 3. A policy applied to all entities of that type." This directly supports that a policy applied to a specific entity (as described in option A) has the highest precedence.