Instrumentation with multiple management servers

You can configure an environment in which multiple management servers deploy policies to nodes that have the HTTPS agent. Every policy on a node is owned by the management server that deployed it. The same ownership concept does not exist for instrumentation.

Management servers all deploy instrumentation to the same folder on managed nodes. You must ensure that one management server does not make inappropriate changes to instrumentation that another management server deployed.

If you need to deploy the same instrumentation from multiple management servers, ensure that all management servers have the same version of the instrumentation. Otherwise, it is possible for one management server to overwrite instrumentation that already exists on a node. For example:

• If you deploy a policy that belongs to a category, the management server deploys the associated instrumentation for that category. If another management server deploys a different policy that belongs to the same category, this management server overwrites the existing instrumentation.
• If you deploy instrumentation explicitly using the console, this can overwrite instrumentation that another management server deployed.

You must also ensure that one management server does not remove instrumentation that is required by another management server's policies. For example :

• If you deploy instrumentation explicitly using the console and set the option to remove all existing instrumentation first, you remove instrumentation that other management servers deployed.
• If you redeploy all policies to a node without setting the ignore owner option, you could remove or replace instrumentation that other management servers deployed.

Related Topics:

• Scalable Architecture for Multiple Management Servers