Installation takes care of AppMon components and their configuration for basic local usage / small implementations. You can have just everything (all AppMon and your components) on one machine and use the stand-alone Collector service / daemon or even the AppMon Server-embedded Collector for a still smaller memory footprint. With more complex, larger deployments you may need quite a number of Collectors. Depending on the architecture of your application the Collectors may be on one or more (virtual) machines. See Embedded Collector Usage Restrictions).
If you run the Collector on a different machine than the AppMon Server you must reference the Server in the registration (Windows) or in the *NIX shell script. See Configure a Collector Other Than Localhost for more information.
To run more than one Collector on a machine you must install extra instances of the installed default instance. If doing this, make sure Collector names and ports used listen for Agents are unique.
Once a Collector is up and connected to the AppMon Server, you can change settings or set up additional ones in the Collector Group by selecting Settings > Dynatrace Server > Collectors in the AppMon Client, then selecting a Collector in the upper pane and configure settings in the lower pane.
The AppMon Collector uses by default 1 GB of memory, which is the demo size for 5 agents. Depending on the number of Agents, you need to adapt this default setting. See the Collector Best Practices for more information.
To change the amount of used memory, open the main configuration file (
dtcollector.ini) in a text editor and adjust the values for the
-Xms parameters. Always use the same value for both parameters, and restart the AppMon Collector to apply your changes.
The following shows an example of an adapted
dtcollector.ini, where memory usage was increased from the default 1 GB to 4 GB (see lines 6,7):
1 ... 2 -basedir 3 collector 4 -restartonfailure 5 -vmargs 6 -Xmx4G 7 -Xms4G 8 ...
See the Deployment Guide for detailed sizing recommendations.
JRE on Solaris, HP-UX, AIX, z/Linux, z/OS
If you install the Collector on HP-UX, AIX, z/Linux, or z/OS, set the Java used to run the Collector. In the
dtcollector.ini file, edit the line after
-vm to point to the Java executable of the desired JRE. For example:
Configure a Collector other than localhost
The configuration settings below can later on be reconfigured in a Collector Group in the AppMon Client by selecting Settings > Dynatrace Server > Collector, then selecting a Collector in the upper pane and configuring settings in the lower pane.
- Unregister the service that was registered by default during installation:
%DT_HOME%/dtcollector.exe -service uninstall
sc delete "dynaTrace Collector 7.0"
- Register the Collector to connect to a AppMon Server on a different machine. The general syntax is:
%DT_HOME%/dtcollector -service install -server <Server(Host)Name>[:PortToConnectToServer] [-listen:PortToListenForAgents]
For example, to register a Collector that connects to an AppMon Server/host named
myAppMonServeron the default port and listens for Agents on the default port:
%DT_HOME%/dtcollector -service install -server myAppMonServer
The registration parameters are reflected in
Linux and Unix
On *NIX there is no automatic registration at install time, so you don't need to unregister a daemon initially. However, to connect to a AppMon Server on a different machine you must at least adapt
DT_OPTARGS= -server myDynatraceServer" in the
$DT_HOME/init.d/dynaTraceCollector shell script, Save As in
/etc/init.d, and register the daemon for boot with
chkconfig or the equivalent on your distribution.
The general syntax is as follows:
DT_OPTARGS="-server <Server(Host)Name>[:PortToConnectToServer] [-listen:PortToListenForAgents]"