The Collectors pane of the Dynatrace Server Settings dialog box allows you to view and configure Collectors, connected to the AppMon Server. To access it, click Settings > Dynatrace Server > Collectors.
|Connected - Collector is connected to server|
|Not Connected - Connection from Server to Collector currently lost|
|Offline - Collector shut down properly.
If a Collector is offline for more than half an hour, it is removed from the list.
|Restart Pending - Collector currently restarting|
|Agent Listening Error - A error with the connected Agents on the Collector|
Select a Collector to configure:
- Collector group
- The Collector-Server connection.
- The Agent-Collector connection.
The rest of the Collector parameters are configured via the Collector configuration file.
Add collector to a group
To add collector to a group, select the group from the Member of Collector Group list, or type the name of a new group and click Apply.
Configure Collector-Server connection
To configure Collector-Server connection, specify the Server host and the port in the Connect to Dynatrace Server at fields. If needed, select the compressed checkbox. Restart the Collector for changes to take effect.
Configure Agent-Collector connection
To configure Agent-Collector connection, specify the port, where the Collector listens to the Agents in the Listen for AppMon Agents at field. The bind address field is optional.
The bind address for the Agent listen port is not configurable if set by system properties in the
dtcollecter.ini file, or as a command-line parameter on AppMon Collector startup. The Collector name stored in the Agent's
CollectorList file is the Collector's detected. If an IP address (multiple NICs in the machine) or fully qualified domain name is required for the Agent to connect to the Collector, you can choose to configure a Collector Bind Address. This bind address is sent to the Agent and populated in its
Click Advanced Configuration to configure multiple bind addresses and/or listening ports for Agent connections to the Collector. Specify them in the Override external addresses textbox.
AppMon requires separate configuration in the one of the following fields:
- AppMon 2017 May Listen for OneAgents at.
- AppMon 2018 April Listen for AppMon Agents at.
AppMon Agent uses secure connection by default, to allow non-secured connections, select the Allow non-TLS on port checkbox, and specify port for such connections.
Restart the Collector for changes to take effect.
AppMon applies collector balancing to make sure that no Collector is overloaded. Collector groups is the instrument to make it happens, allowing Agent connection balancing/switch-over (but no automatic switch-back) across Collectors in the same group. If the agent balancing task realizes that a Collector is overloaded, it tries to move agents to other collectors within the same group. By default, collectors with a load of more than 50% of the group average are considered overloaded.
Collectors without a group name are standalone Collectors. No Agent connection balancing is performed across them.
At start an Agent always tries to connect to the Collector, specified in the Agent connection string. If this Collector is overloaded, the Agent gets a list of available Collectors in the group, and reconnects randomly.
If a Collector goes down for any reason such as a service problem, connection issue, host failure, or manual restart, the connected Agents try to reconnect for 20 seconds. If they can't reconnect during that time span, the Agents switch over to a different Collector in that group. If connection to the new Collector is operating, Agents do not switch back when their original Collector becomes available again. However, they switch back or redistribute when the applications or Agents restart.
Despite automatic balancing, you should not point all the Agents to one Collector for initial connection, but distribute as you would manually.
Obey the Agents-per-Collector-limits that apply for different technologies, calculate the sum for the group and have sufficient reserve for switch-over. With large, diverse networks, plan which Collector groups and respective Agents should be close to each other.
Clearing Collector caches
The Collector performs daily cleanup to keep the class cache from growing too large. The cache purges Classes not used for a week.
If your class cache is corrupted and you must clear it immediately, contact support.