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.
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 FROM command:
COPY --from=<environmentURL>/linux/oneagent-codemodules:<TECHNOLOGY> / /ENV LD_PRELOAD /opt/dynatrace/oneagent/agent/lib64/liboneagentproc.so
where:
<environmentURL> is:
<ActiveGateaddress:9999>{yourenvid}.live.dynatrace.com<TECHNOLOGY> is the OneAgent code module required for your application. Valid options are all, java, apache, nginx, nodejs, dotnet, php, go, and sdk. To specify several code modules, separate them by hyphens (for example, use java-go to specify java and go). 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: equals tenantUUIDDT_TENANTTOKEN: equals tenantTokenDT_CONNECTION_POINT: semi-colon separated list of communicationEndpointsYou can configure network zones as an environment variable:
DT_NETWORK_ZONE: equals your.network.zoneSee network zones for more information.
optional Configure a proxy address
In case you run an environment with proxy, you need to set the DT_PROXY environment variable in the application container to pass the proxy credentials to OneAgent.
For Alpine Linux-based containers, you might need to update the wget shipped with the Alpine image to allow for proxy authentication for the download of 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.
To uninstall OneAgent from application-only monitoring, just remove references from your application or Docker image and then redeploy the application.