Install Collectors

This page details installing Collector instances and covers critical information needed before installation. It also covers embedded Collector restrictions.

For troubleshooting tips, click here.

What to know before Collector installation

All platforms

  • A Collector should always be placed close (in terms of latency) to the connected Agents. There are thousands of start-up round-trips between them to instrument application classes. A Collector should be placed in the same sub-net, or at least in the same data center as the Agents and instrumented applications. This allows connecting to the AppMon Server over the WAN if needed.

  • The number of Collectors is not the exclusive sizing factor, but also JVM heap memory and the number of cores (and naturally disk space) available to a Collector process determines the number of Agents it can take. Also, Collectors need a lot more heap and disk space (for class cache and inheritance map) if the instrumented applications are different, so applications should be hooked to Collector groups according to their similarity. Sensible grouping of apps and equally sized Collectors in a group are also prerequisite for Collector - Agent load balancing. See Collector Best Practices to adapt settings when your requirements change or ask sales or support.

Collector installation directory

This table lists directories of special interest created when installing a Collector.

Relative path Description
DT_HOME The executables and the main configuration file dtcollector.ini.
DT_HOME\log\collector Log files.
DT_HOME\collector\cache Class cache directory.
DT_HOME\collector\conf Main configuration directory.

Install collectors

Windows

Download the full Windows installation package for your architecture. Do a custom installation if you only need the Collector.

The setup defaults to an installation path (%DT_HOME>) of C:\Program Files\Dynatrace\Dynatrace 7.0.

Installation creates Start menu entries and registers an auto-starting Windows service, configured to connect to an AppMon Server on the same machine (localhost) on the default port (6698 or 6699 (SSL)) and name (AppMon Collector 7.0).

Install extra collector instances

The Collector names (Windows: service names) and the ports each Collector listens for Agents must be unique.

If you want your Collector instance to connect to a specific Server other than localhost, add -server <dynaTraceServerName> to the registration (Windows) or shell script (Linux/Unix).

The first start of the new Collector instance creates the directory structure <DT_HOME>\collector\instances\<CollectorInstanceName> that replicates the structure of the default instance and copies the files from there.

Windows

This sample code shows how to register and start a new service called Dynatrace Collector 7.0 (MyCollector) that listens for classic Agent connections on port 9997 and AppMon Agents on port 8044:

CD %DT_HOME%
dtcollector -service install -instance MyCollector -listen :9997 -listenHttp :8044
sc start "Dynatrace Collector  (MyCollector)"

To register an extra Collector service instance that listens for classic Agents on port 9997, AppMon Agents on port 8044 and connects to myAppMonServer (on a different machine):

dtcollector -service install -instance MyCollector -listen :9997 -listenHttp :8044 -server myAppMonServer

To un-register a Collector instance, for example to possibly re-register it with new arguments:

sc stop "Dynatrace Collector 7.0 (MyCollector)"
sc delete "Dynatrace Collector 7.0 (MyCollector)"

or

%DT_HOME%/dtcollector -service uninstall -instance MyCollector

Agent connection balancing

See the Collector Groups section to learn how to balance the load between several Collectors.

Automatic installation

You can automate the installation with Ansible, Chef, or Puppet. Click the link below for more detailed information.

Embedded collector usage restrictions

The AppMon Server includes an embedded (as opposed to stand-alone) Collector that should only be used for testing purposes. The embedded Collector is started in-process with the Server, a stand-alone Collector service / daemon must be explicitly started. Enable the embedded Collector in the Client by selecting Settings > Dynatrace Server > Services and selecting the Allow Agent Connections to Dynatrace Server check box under Embedded Collector Settings. You must restart the AppMon Server after changing this setting.

The table indicates whether the embedded Collector can (Yes) or cannot (No) be used by different AppMon editions in different (license) scenarios.

Edition or
Installation type
Production Pre-production (aka Test Center) Dev team
(discontinued)
POC Yes Yes Yes
Evaluation Yes Yes Yes
Perpetual No No No
Term No No No