Process of Configuring Agent - Enterprise Manager Network Topology

 
apmdevops106
Configuring agent to Enterprise Manager network topology requires these high-level steps.
  1. Configure the introscopenenterprisemanager.properties file if appropriate for your deployment.
  2. Configure the IntroscopeAgent.profile file if appropriate for your deployment.
  3. Configure loadbalancing.xml.
    1. (Optional) Configure the latch property so that specific agents always connect to specific Enterprise Managers.
    2. (Optional) Configure include and exclude elements to allow and disallow agent connections to specific Enterprise Managers.
    3. Save loadbalancing.xml.
    The new values go into effect when the Enterprise Manager checks the property file during a hot deploy, which occurs about every 60 seconds. The MOM sends the updated loadbalancing.xml to Collectors in the cluster at the next load balance interval.
  4. Perform system monitoring and reconfigure if needed.
    1. Reconfigure any properties as needed.
    2. Update loadbalancing.xml.
Plan the Agent - Enterprise Manager Network Topology
Plan your agent to Enterprise Manager or Collector topology before configuring agent connection assignments. In these assignments, you configure which agents are allowed or not allowed to connect to specific individual or groups of Collectors.
If your business practices require it, set up agents into subclusters. You can assign agents to a specific set of Collectors, and then configure loadbalancing.xml so the MOM load balances only that set of Collectors. For example, you could have the agents monitoring the applications for a specific business unit connect to three Collectors in your cluster of ten.
During your planning, ask and answer questions such as:
  • Are classes or groups of agents or specific agents allowed or disallowed in the cluster or on specific Collectors?
  • Should any Collector be specially protected against overloading?
    For example, do some Collectors need protection against direct connections from mis-configured agents? If all agents have identical agent profiles and attempt to connect, they may flood a single IP address. Too many agents connected to a Collector can crash that Collector.
Follow these steps:
  1. For each group or class of agent, determine which set of Collectors you want to:
    1. Allow access.
    2. Disallow access.
  2. Determine the default connection activity of agents that are not matched in loadbalancing.xml.
    Do you want to allow or disallow all agents that are not matched in loadbalancing.xml on specific Enterprise Managers?
  3. Will any agents be load balanced? If so, are they allowed on all the Collectors that you want them moved to?
    Carefully consider the effect of agent connection restrictions, as they restrict the load balancing options for the MOM. A MOM performing load balancing cannot remove an agent from an overloaded Collector when the agent is not allowed to connect to an under-loaded Collector. In this case, the MOM must load balance other agents from the overloaded Collector to an under-loaded Collector.
  4. Determine how agents disconnected from an Enterprise Manager will act.
    Do you want agents to try to reconnect continuously to any allowed Enterprise Manager?
    Or based on the agent CA APM version is it better for:
    • Valid for pre-9.1 agents:
      Disconnect from an Enterprise Manager and keep trying to reconnect?
    • Valid for 9.1 and later agents:
      Remain passively connected to the final allowed Enterprise Manager on the agent Allowed Enterprise Manager list?
      Passively connected agents have these characteristics:
      • Do not send any metric data to the Enterprise Manager.
      • Do not try to reconnect to other Enterprise Managers that become available.
  5. Does your CA APM environment allow agents to connect across the following CA APM components:
    • Clusters?
    • Collectors and Standalone Enterprise Managers?
    • Any combination of clusters, Collectors, and Standalone Enterprise Managers?