Dynatrace AppMon 6.5 Documentation

Other Doc Versions & KB

Skip to end of metadata
Go to start of metadata


For a comparison of what you can monitor with traditional plugins vs. Agents, see Monitoring - Agent-based since 4.2To install the Host Monitoring Agent, you can use either the full installer or the Agent installer for your platform.


Note: You only need a Host Monitoring Agent if no other Agent runs on that particular machine, because any other active Agent (except the Node.js one) delivers those metrics.
The Web Server master Agent only delivers when a slave / sub- Agent is connected to it.

With a lot of Agents on one machine you might get into the situation where you want to switch off delivery of host monitoring data from non-Host-Agents to reduce traffic from Agent to Collector. Please consult support for the best strategy.

Beginning with the AppMon 5.0 Agent loader / bootstrapper you can restart Host Agents from the Client's Agent Overview / Status dashboard > Host Agent context menu.

Process Availability Monitoring

With AppMon 6.5, the Host Monitoring Agent is capable to monitor the availability of any process running on the host. For further information on process availability monitoring see configuration of hosts/host groups

Installation and Configuration


With the full installer, the Host Agent was previously registered as an auto-starting service at install time. However, for AppMon 5.6 and later:

  • with the full installer, the Host Agent is installed, but the service is no longer registered due to the potential redundant Host Agent role mentioned previously. 
    You can register the Host Agent with "<DT_HOME> \agent\lib\dthostagent" -service install

    Copy/paste example for 32-bit Host Agent service from a 64-bit AppMon full installation:
    "C:\Program Files\dynaTrace\dynaTrace 6.5\agent\lib\dthostagent" -service install

    Unregister the Agent with sc delete "dynaTrace Host Agent 6.5"

  • with the Agent-only installer, you need to do a custom install for the Host Agent to be installed and registered for auto-start. The use case would be to monitor the machine with no other Agent running on it.
    The default <DT_HOME> is C:\Program Files (x86)\dynaTrace\dynaTrace Agent 6.5, still including the 64-bit libraries in agent\lib64.

On *NIX, cd /opt and java -jar <DownloadDir>/<dynatrace(Agent)Installer.jar>. The installer will default to the current directory and ask if you want to change the destination. Make sure you have the right permissions for installation and the target.
<DT_HOME> will be /opt/dynatrace-6.5 or /opt/dynatrace-agent-6.5, depending on the full or Agent-only installer respectively.

The <DT_HOME>/init.d/dynaTraceHostAgent shell script should be copied to or referenced in (link) /etc/init.d and added to system boot by something like chkconfig or update-rc.d, depending on your distribution.

Configuration must be done by editing the <DT_HOME>/agent/conf/dthostagent.ini:






Agent name, can be used to map an Agent to a specific Agent Group.



The AppMon standalone or Server-embedded Collector to which this Agent should connect.
Background: The Collector used to be Server-integrated. That´s where the argument name "Server" stems from. Most licenses allow only standalone Collectors– except for testing.



Define log level.



Define console log level.


<agent location>/log

Specify a custom log file.


<not set>

Specify a custom hostname, if set this prevents the Agent from auto detecting the hostname.

Example Basic dthostagent.ini

The following is an example <DT_HOME>/agent/conf/dthostagent.ini file. This file configures the Host Monitoring Agent named host (default) to connect to the AppMon Server (actually stand-alone or Server-integrated / embeddedCollector ) with the fully qualified name dtcollector.localdomain.com on port 9998.


Agent Bulk Installation

To monitor hosts in the hundreds, you can automate the Host Agent deployment. See below for more details.


You can do a silent (custom) installation with the full or Agent-only .msi or use dthostagent.exe and dtagentcore.dll and dthostagent.ini in the above mentioned directory structure.

If you use the installer with msiexec /passive /i <path>\<dynaTraceInstallerFileName>.msi ADDLOCAL="HostAgent", then the Host Agent is registered as an auto-starting service with the default settings from dthostagent.ini.
You can rewrite dthostagent.ini and un/register the service with the new arguments.

If you just use the .exe and .dll you can write your own dthostagent.ini and register the service to auto-start with <DT_HOME>\agent\dthostagent.exe -service install.

#extract dthostagent and libdtagentcore.so from agent/lib64/ in the jar
#extract init.d/dynaTraceHostagent from the jar
#mimic Agent directory structure on the host
mkdir dynatrace-agent- 6.5 . 0
mkdir dynatrace-agent- 6.5 . 0 /agent
mkdir dynatrace-agent- 6.5 . 0 /agent/lib64
mkdir dynatrace-agent- 6.5 . 0 /agent/conf
#copy dthostagent and libdtagentcore.so to agent/lib64/
#write a basic dthostagent.ini (see above) to agent/conf
#copy dynaTraceHostagent shell script to /etc/init.d
#be sure the Name specified in dthostagent.ini is mapped in some tier to avoid an error message
# try the Agent before you add it to boot
#/etc/init.d/dynaTraceHostagent start
chkconfig add dynaTraceHostagent