To install Dynatrace OneAgent when you have a Dynatrace SaaS deployment, go to Dynatrace.com and Login using the username and password you received from Dynatrace in your signup confirmation email. If you have a Dynatrace Managed deployment, access the Cluster Management Console and choose the environment you want to monitor. Then continue with the installation steps provided below.
Ensure that your firewall settings allow communication to Dynatrace.
Depending on your firewall policy, you may need to explicitly allow certain outgoing connections. The remote Dynatrace addresses to add to the allow list are given on the installation page for OneAgent.
In Dynatrace Hub, select OneAgent.
Select Set up > Linux.
Choose the PowerPC (BE) installer type from the list. Copy the command provided in the Use this command on the target host to download OneAgent for Linux PowerPC (BE) text field
Login to your PPC BE Linux host and execute the command you copied from Dynatrace.
wget
to access the server. You can also download the ZIP archive of OneAgent by clicking the Download OneAgent installer link in the page footer and saving the installer script to any location; this bypasses the wget
command altogether.In your file system, create a folder for OneAgent installation. For example, /opt/dynatrace/oneagent
.
Unzip the ZIP archive of OneAgent into the newly created folder.
All monitored applications must to be able to read the OneAgent library. Ensure that the permissions allow this.
You have two options now: either monitor every application on your host or just a single application.
To automatically monitor every application on your host, enable the liboneagentproc.so
component of OneAgent. This is located in the system library directory (/lib
or /lib64
depending on your architecture), at /etc/ld.so.preload
.
Great, the setup is complete! You can now take a look around your new monitoring environment. You can access your monitoring environment anytime by going to Dynatrace website and selecting Login in the upper-right corner.
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 go to Deployment Status, switch to the All hosts or Recently connected hosts tab, and expand the host you are interested in.