Configure Agent Continual Reconnect to Any Allowed Enterprise Manager

You can configure whether agents that are denied connections on all Enterprise Managers to continually cycle through their Allowed Enterprise Manager list trying to reconnect. The following are the allowed Enterprise Managers:
apmdevops106
You can configure whether agents that are denied connections on all Enterprise Managers to continually cycle through their Allowed Enterprise Manager list trying to reconnect. The following are the allowed Enterprise Managers:
  • Enterprise Managers configured in the agent profile introscope.agent.enterprisemanager.connectionorder property value.
  • Any Enterprise Manager allowed based on loadbalancing.xml configuration.
If a denied agent cannot connect to an Enterprise Manager, it handles connections in these ways:
  • Tries to connect to the next allowed Enterprise Manager on the Allowed Enterprise Manager List.
  • Does not connect to any Enterprise Manager on which it is configured as disallowed.
Configuring denied agents to keep trying to connect has these characteristics:
  • Is useful for environments where agents are allowed to connect across these Introscope components:
    • Clusters.
    • Collectors and Standalone Enterprise Managers.
    • Any combination of clusters, Collectors, and Standalone Enterprise Managers.
  • Forces disconnected agents to keep trying to connect to allowed Enterprise Managers under these conditions:
    • Until an Enterprise Manager is available for connection.
    • Even if the Enterprise Managers are in different clusters.
    Otherwise, agents handle connections in these ways:
    • Passively connect to an Enterprise Manager and do not send metric data.
    • Do not try to connect to allowed Enterprise Managers, including any that becomes available after being not available.
Follow these steps:
  1. Open the IntroscopeAgent.profile file.
  2. Set the introscope.agent.enterprisemanager.failbackRetryIntervalInSeconds property.
  3. Save the IntroscopeEnterpriseManager.properties file.
  4. Restart the managed application.
    If these events occur:
    • Agent is denied connection to an Enterprise Manager
    • Enterprise Manager is down
    Then the agent immediately tries to connect to the next allowed Enterprise Manager on the Allowed Enterprise Manager List.
    If the agent cannot connect to any allowed Enterprise Manager, then the agent performs these actions:
    • Waits for the duration set in the introscope.agent.enterprisemanager.failbackRetryIntervalInSeconds property.
    • Retries connecting to allowed Enterprise Managers starting with the first Enterprise Manager on its Allowed Enterprise Manager List.
    This cycle repeats until the agent connects to an Enterprise Manager to which it can actively send data.