Set up OneAgent on containers for application-only monitoring
If you don't have access to underlying hosts, you can deploy OneAgent on containers for application-only monitoring. Follow the steps below to integrate OneAgent into the application image.
Deploy OneAgent
- Docker version 17.05+
-
Sign in to Docker with your Dynatrace environment ID as username.
docker login <environmentURL> -u <environmentID> -
Enter your <PAAS_TOKEN> when prompted.
-
Add the following lines of code to the application image, after the last
FROMcommand:COPY --from=<environmentURL>/linux/oneagent-codemodules:<TECHNOLOGY> / /ENV LD_PRELOAD /opt/dynatrace/oneagent/agent/lib64/liboneagentproc.sowhere:
<environmentURL>is:- Environment ActiveGate:
<ActiveGateaddress:9999> - SaaS:
{yourenvid}.live.dynatrace.com
- Environment ActiveGate:
<TECHNOLOGY>is the OneAgent code module required for your application. Valid options areall,java,apache,nginx,nodejs,dotnet,php,go, andsdk. To specify several code modules, separate them by hyphens (for example, usejava-goto specifyjavaandgo). Including specific technology-support options, rather than support for all technology options, results in a smaller OneAgent package.
Dynatrace OneAgent supports Alpine Linux–based environments.
Use this syntax:
COPY --from=<ACTIVEGATE-ADDRESS>/linux/oneagent-codemodules-musl:<TECHNOLOGY> / /ENV LD_PRELOAD /opt/dynatrace/oneagent/agent/lib64/liboneagentproc.so
Valid options here are all, dotnet, php, java, apache, nginx, nodejs, and go.
-
Build your application image.
Build the Docker image from your Dockerfile to use it in your Kubernetes environment.
docker build -t yourapp .You can monitor your application containers with a different Dynatrace environment.
For OneAgent version 1.139+, if you have an existing application image where you've already added the OneAgent code modules for a specific Dynatrace environment, you can have the OneAgent report to another Dynatrace environment without rebuilding your application image.
For this, you need to make a call to the REST endpoint of your second Dynatrace environment. Don't forget to adapt the respective placeholders<environmentID>and<token>.curl "https://<environmentID>.live.dynatrace.com/api/v1/deployment/installer/agent/connectioninfo?Api-Token=<token>"In return, you get a JSON object that covers the required information that needs to be passed as an environment variable to the application container.
Make sure you set the environment variables of the application container as described below:DT_TENANT: equalstenantUUIDDT_TENANTTOKEN: equalstenantTokenDT_CONNECTION_POINT: semi-colon separated list ofcommunicationEndpoints
- optional Configure network zones
You can configure network zones as an environment variable:
DT_NETWORK_ZONE: equalsyour.network.zone
See network zones for more information.
-
optional Configure a proxy address
In case you run an environment with proxy, you need to set the
DT_PROXYenvironment variable in the application container to pass the proxy credentials to OneAgent.For Alpine Linux-based containers, you might need to update the
wgetshipped with the Alpine image to allow for proxy authentication for the download of OneAgent.
Update OneAgent
Each time you want to leverage a new version of Dynatrace OneAgent, you must rebuild your local OneAgent code modules and application image. Any newly started pods from this application image will be monitored with the latest version of OneAgent.
If you've specified a default OneAgent installation version for new hosts and applications using OneAgent update settings, your Kubernetes applications will be automatically monitored by the defined default version of Dynatrace OneAgent.
Uninstall OneAgent
To uninstall OneAgent from application-only monitoring, just remove references from your application or Docker image and then redeploy the application.