This page describes how to download and install Dynatrace OneAgent on Linux.
- If you're a Dynatrace SaaS customer, go to Dynatrace.com, click SaaS login, and sign in using the username and password you received from Dynatrace in your signup confirmation email.
- If you're a Dynatrace Managed customer, access the Cluster Management Console and choose the environment you want to monitor.
Then continue with the installation steps provided below.
- You need administrator rights for the servers where Dynatrace OneAgent will be installed and for changing firewall settings (necessary only if your internal routing policy may prevent Dynatrace software from reaching the internet).
- You need permissions and credentials for restarting all your application services.
- You need to check the disk space requirements.
- The host on which you install OneAgent needs at least 300 MB RAM.
- There are certain limitations when deploying OneAgent on a Linux host with mounted NFS drives. See Troubleshoot OneAgent installation.
- All hosts that are to be monitored need to be able to send data to the Dynatrace cluster. Depending on whether your Dynatrace environment is a SaaS or a Managed deployment, and depending on your network layout and security settings, you can choose to either provide direct access to the Dynatrace cluster, or you can set up an ActiveGate.
Select Deploy Dynatrace from the navigation menu.
Select Start installation and choose Linux.
Choose the installer type from the list. Use the Linux shell script installer on any Linux system that's supported by Dynatrace, regardless of the packaging system your distribution depends on.
Copy the command provided in the Use this command on the target host text field.
Paste the command into your terminal window and execute it.
After the download is complete, verify the signature:
- Copy the command from the Verify signature text field.
- Paste the command into your terminal window and execute it. Make sure your system is up to date, especially SSL and related certificate libraries.
Copy the command provided in the And run the installer with root rights text field.
If your environment is segmented (for example, into development and production), consider organizing your hosts into host groups.
Paste the command into your terminal window and execute it. Note that you’ll need root access. You’ll need to make the script executable before you can run it. You can use
sudo to run the installation script. To do this, type one of the following commands into the directory where you downloaded the installation script.
sudo /bin/sh Dynatrace-OneAgent-Linux-1.0.0.sh
su -c '/bin/sh Dynatrace-OneAgent-Linux-1.0.0.sh'
Dynatrace OneAgent v1.141+ can be installed in non-privileged mode. This is the only time you need to grant elevated privileges to Dynatrace OneAgent. Elevated privileges are dropped as soon as Dynatrace OneAgent is deployed. To install Dynatrace OneAgent in non-privileged mode, you need to manually append the
NON_ROOT_MODE=1 parameter to the installation command. For example:
sudo /bin/sh Dynatrace-OneAgent-Linux-1.0.0.sh NON_ROOT_MODE=1
To install OneAgent in non-privileged mode, your system must meet specific requirements. For more information, see Linux non-privileged mode.
- If you plan to download Dynatrace OneAgent directly to a server, note that outdated or missing libraries (for example, CA certificates or OpenSSL) prevent the installer from downloading.
- Dynatrace uses encrypted connections. OpenSSL is required to enable
wgetto access the server. You can also download the installer by clicking Download OneAgent installer in the page footer and saving the installer script to any location you want, which bypasses the
Dynatrace OneAgent is a set of specialized services configured specifically for your monitoring environment. The role of these services is to monitor various aspects of your hosts, including hardware, operating system, and application processes.
During the installation process, the installer:
Installs executable code and libraries that are used by Dynatrace OneAgent. OneAgent binaries are installed in the
/opt/dynatrace/oneagentdirectory and startup scripts are created in
/etc/init.d(on systemd systems, startup scripts are created in
/etc/systemd/system/). One of the Linux OneAgent components,
liboneagentproc.so, is located in the system library directory (
/lib64depending on your architecture) and is enabled at
For OneAgent versions 102 and earlier, Linux OneAgent binaries are installed at
/opt/ruxit/agent/and the specified Linux OneAgent component is called
Creates its own user (
dtuser). This user is created without a password. It's not possible to login with this user. For security purposes, services that don’t require root privileges will run under this user. Installation, however, still requires root access.
Checks the system’s global proxy settings.
Checks for a connection to Dynatrace Server or ActiveGate (if you installed ActiveGate and downloaded the OneAgent installer after ActiveGate was connected to Dynatrace).
Detects all SELinux-aware applications and adjusts the SELinux security policy accordingly.
Allows Dynatrace OneAgent to inject its own libraries into monitored processes.
Modifies the core pattern configuration so that OneAgent can detect and report process crashes. The original core_pattern configuration will still work following installation and will be preserved in
/opt/dynatrace/oneagent/agent/conf/original_core_pattern, where you can define your own core settings using the format as specified in Linux Programmer's Manual.
For a summarized view of the changes made in your system's files by OneAgent installation, see Changes on Linux files page.
Great, setup is complete! You can now take a look around your new monitoring environment. If you are a SaaS customer, you can access your monitoring environment anytime by going to Dynatrace website and clicking the Login button in the upper-right corner. If you are a Managed customer, you can access your monitoring environment through the Cluster Management Console.
One last thing: to monitor your processes, you need to restart them. At any time, you can check which processes aren't monitored and need to be restarted. Just select Deployment status from the navigation menu, click the All hosts or Recently connected hosts tab, and expand the host you are interested in.