On Windows, you can control the AppMon Collector from the Start menu, command line, or Services control panel. The registered service name is Dynatrace Collector <version> [(<instanceName>)].
For example, to start the Collector, execute:
sc start "Dynatrace Collector 7.0"
To configure the service to start automatically on system startup, execute:
sc config "Dynatrace Collector 7.0" start= auto
There is no space between
=, but there must be a space after
Alternatively, you can start the Collector from the command line:
cd %DT_HOME% dtcollector.exe -service start
See Install extra collector instances to learn how to start more than one Collector instance on one machine.
For testing purposes, you can interactively start the AppMon Collector in the background (
-bg) by using the launcher
dtcollector. The following commands start a Collector that listens on
localhost for Agents on default port 9998 and connects to an AppMon Server at default port 6698:
cd $DT_HOME ./dtcollector -bg
You can use
<DT_HOME>/init.d/dynaTraceCollector start | stop | status to stop or check the Collector without caring about its pid.
For normal operations, you should use the
<DT_HOME>/init.d/dynaTraceCollector script that starts the Collector on the desired run levels at boot time. For Linux, you can use the script without changes: Copy it to
/etc/init.d and add it to boot time with
chkconfig --add dynaTraceCollector.
To detect any running AppMon Collector instance, the
init script checks for a file
dtcollector.pid located in
If an instance name is being used, the corresponding
.pid file is called:
/var/run/dtcollector.<instance>.pid. If the
.pid file is not present for some reason, such as missing write permissions to
/var/run, the script tries to find the process ID by grepping the
ps output for running
dtcollector instances. You may need to change
grep arguments to get the right Collector instance, which might be tricky when an instance name is being used. Therefore, it is strongly recommended to configure the system so that
.pid files can be used.
dtcollector -? renders the supported arguments.
dynaTrace Collector Version: ... - built ... Copyright (C) 2004-20.., dynaTrace software GmbH Usage: dtcollector [options] Available options: -?, -h, --help Print this help message -v Display version information -loglevel [0..8] Set loglevel, valid values are: [0..8] or [finest|finer|fine|config|info|warning|severe|debug|none] Default setting: 4 (info) -basedir <dir> Set working directory for application -ini <config> ini file to use, default is dtcollector.ini A value of 'ignore' skips reading the .ini file. -instance <name> Instance name for this Collector instance -listen [<ip>:]<port> Listen for dynaTrace Agents on [<ip>:]<port> -server <host>[:<port>] Connect to dynaTrace Server at <host>[:<port>] -service [install | uninstall | start | stop | list(all)] Install/uninstall Windows Service (uninstall might require you to log off) -timeout <sec> Timeout value for watchdog feature, 0 turns the watchdog off. Default value: 180, valid value range [30..86400] sec -portrange <n>[:<m>] Port range to be used by watchdog feature By default a port within range 50000:65535 is used -vm <javaVM> The Java VM to be used for launching the application -startup <startup.jar> The startup jar to execute. The default is to find the plugins/org.eclipse.equinox.launcher jar with the highest version number. -ea[:<package>"..."|:<class>] Enable assertions (assertions are disabled by default). A <package> or <class> name can be specified (cf. Java docs) -osgicleanonrestart Clean OSGI cache on restart (set system property osgi.clean=true if application gets restarted) -Dosgi.\*=<value> Set arbitrary OSGI configuration parameters -D\*=<value> Set properties for Java application -X\*=<value> Set (nonstandard) options for Java VM