Agent - Enterprise Manager Network Topology Overview

The goal of planning and configuring your agent - Enterprise Manager network topology is to prevent or reduce CA APM performance issues. Such as preventing these example situations:
apmdevops106
The goal of planning and configuring your agent - Enterprise Manager network topology is to prevent or reduce CA APM performance issues. Such as preventing these example situations:
  • New agents from randomly being started up and flooding a specific Collector with connections.
  • Agents in a test environment from connecting to your production environment.
You can use these files and properties to control how and when agents connect to specific standalone Enterprise Managers or Collectors:
  • loadbalancing.xml file.
  • introscope.apm.agentcontrol.agent.allowed property in the EnterpriseManager.properties file.
  • introscope.agent.enterprisemanager.failbackRetryIntervalInSeconds property in the IntroscopeAgent.profile file.
When you configure MOM agent load balancing in loadbalancing.xml, you tell the MOM where to move agents based on these factors:
  • Collector capacity.
  • Number of agent metrics being produced.
  • Collector capacity weighting factors.
Example
Your environment consists of a MOM and five Collectors. You want agent 1 and agent 2 to be load balanced on Collector 1 and Collector 2. You configure loadbalancing.xml for these agent to Enterprise Manager connections:
  • Allow agent 1 and agent 2 to connect to Collectors 1 and 2.
  • Do not allow these agents to connect to Collectors 3, 4, and 5.
If there is an overload, the MOM handles the agents as follows:
  • Allocates agent 1 and agent 2 on Collector 1 and Collector 2 depending on the runtime cluster load.
  • Never allows these agents to connect to Collectors 3, 4, or 5.
You can also use loadbalancing.xml for fine-grained agent to Enterprise Manager connection setting, which the MOM then carries out across the cluster. This chapter describes how you can implement fine-grained agent to Enterprise Manager connections.
The MOM sends to each Collector the agent allow and disallow connection rules set in loadbalancing.xml upon startup and every 10 minutes. Collectors use these rules to know which agents to accept and deny when the agents request to connect. Collectors send the rules to each agent so each agent knows what to Collectors it can connect when these actions occur:
  • MOM goes down.
  • A Collector denies the agent connection request based on a disallow configuration setting.
If an agent is denied connection to an Enterprise Manager, then the APM Status console Denied Agents list displays an entry. If an agent is passively connected to an Enterprise Manager and not sending data, the APM Status console Denied Agents list also displays an entry.
You can use the APM Status console Denied Agents list to monitor for repeated denied and passive connections on specific agents or groups of agents. You can then configure loadbalancing.xml to allow the denied or passive agents to connect to a different Collector.