The xAgent Policy Service generates a final configuration for each agent in your environment. The final xAgent configuration is based on the host set assignment and the priority order of the custom policies assigned. The table below shows an example of the xAgent and the host set relationship, the priority level assigned to each policy, and the policy assignments defined for each host set.
.png)
Each xAgent is paired with a host endpoint and assigned to one or more host sets. Each policy is assigned a distinct priority level and each host set is assigned specific policies. Based on these factors, the final configuration applied to xAgent 1 is a composite policy defined by the xAgent Default Policy, the Migrated Policy, and Custom Policy 2. This policy prioritizes and applies policy settings in the following order:
Custom Policy 2 (Priority 1)
Migrated Policy (Priority 2)
xAgent Default Policy (Priority 3)
The example above also shows that xAgent 2 is assigned to Host Set A and Host Set B. The final configuration applied to this xAgent is also a composite policy that pulls in the policies assigned to both host sets. In this example, the composite policy uses the policy priority levels to define the overall policy order below:
Custom Policy 3 (Priority 1)
Custom Policy 2 (Priority 2)
Custom Policy 1 (Priority 3)
Migrated Policy (Priority 4)
xAgent Default Policy (Priority 5)
When a host endpoint comes online for the first time, it receives all the xAgent policies mapped to its host set assignments, including the xAgent default policy. If a host endpoint is added to a new host set or removed from an existing host set, the xAgent Policy Service generates a new xAgent configuration based on the new host set assignment and sends it to the host endpoint. This final xAgent configuration may differ from the previous configuration.