Configure Agent to Collector Connections for Load Balancing

When any Collector gets overloaded, the MOM can disconnect and redirect any agents to rebalance the cluster. The MOM uses weighting properties and loadbalancing.xml to handle the load balancing. To avoid the MOM disconnecting and redirecting the agents, define the agent to Collector connections in loadbalancing.xml. Optionally you can configure the MOM host name or IP address in IntroscopeAgent.profile to allow the MOM to load balance the agents.
apmdevops106
When any Collector gets overloaded, the MOM can disconnect and redirect any agents to rebalance the cluster. The MOM uses weighting properties and loadbalancing.xml to handle the load balancing. To avoid the MOM disconnecting and redirecting the agents, define the agent to Collector connections in loadbalancing.xml. Optionally you can configure the MOM host name or IP address in IntroscopeAgent.profile to allow the MOM to load balance the agents.
Define Agent to Collector Connections
When you require agents to connect only to specific Collectors, configure load balancing.xml.
When you have agent to Collector connections defined in the IntroscopeAgent.profile, you can run this CLW command:
autoprepare loadbalancing.xml
This command adds the agent to Collector connection information to the existing loadbalancing.xml file. Run the command before
upgrading the agents.
Follow these steps:
  1. Upgrade the MOM and Collectors.
  2. Back up loadbalancing.xml.
    • If there are existing configurations in loadbalacing.xml, navigate to the MOM <EM_Home>/config directory and back up the file.
    The MOM deletes existing loadbalancing.xml comments when running the autoprepare loadbalancing.xml process. The MOM preserves the existing agent to Collector connection information.
  3. Be sure that all agents that are configured in IntroscopeAgent.profile to connect directly to a Collector are running and connected to their Collectors.
  4. On the MOM computer, run this CLW command: 
    autoprepare loadbalancing.xml
    Run this command after the MOM and all the Collectors are upgraded to the current release and before the agents are upgraded. If you run the command after the agents are upgraded, the MOM cannot gather the former agent to Collector connection information.
    The MOM collects the runtime information about all the agents that are connected directly to the Collectors. The MOM populates the connection information at the bottom of loadbalancing.xml.
    The MOM cannot collect the agent connection information for that Collector in two situations. The MOM cannot collect the connection information when the Collector is stopped or the Collector is not connected to the MOM. Loadbalancing.xml is not updated with that information.
  5. Optional: When a Collector is stopped or not connected to the MOM, update loadbalancing.xml using one of these methods:
    1. Manually add the agent-Collector information to loadbalancing.xml.
    2. Restore the loadbalancing.xml backup file and run the command again with all the agents that are connected to all the Collectors.
Load Balancing Example
An organization has agents that are assigned to Collectors as shown in this table.
Agent Name
Collector Name
AgentA
Collector01
AgentB
Collector01
AgentC
Collector02
AgentD
Collector02
AgentE
Collector03
AgentF
Collector03
The organization uses loadbalancing.xml to load balance an agent named EPAgent2.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <loadbalancing xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="loadbalancing0.1.xsd"> <agent-collector name="Example 1"> <agent-specifier>.*\|.*\|EPAgent2</agent-specifier> <exclude> <collector latched="false" port="5001" host="Collector02"/> </exclude> </agent-collector> <agent-collector name="[email protected] auto-generated configuration"> <agent-specifier>HostName|ProcessName|AgentA</agent-specifier> <agent-specifier>HostName|ProcessName|AgentB</agent-specifier> <include> <collector latched="false" port="5001" host="Collector01"/> </include> </agent-collector> <agent-collector name="[email protected] auto-generated configuration"> <agent-specifier>HostName|ProcessName|AgentC</agent-specifier> <agent-specifier>HostName|ProcessName|AgentD</agent-specifier> <include> <collector latched="false" port="5001" host="Collector02"/> </include> </agent-collector> <agent-collector name="[email protected] auto-generated configuration"> <agent-specifier>HostName|ProcessName|AgentE</agent-specifier> <agent-specifier>HostName|ProcessName|AgentF</agent-specifier> <include> <collector latched="false" port="5001" host="Collector03"/> </include> </agent-collector> </loadbalancing>
Example 1 was a loadbalancing.xml entry before the Administrator ran the command. The MOM added the auto-generated entries after Example 1.