To monitor applications running on managed Kubernetes environments, integrate Dynatrace OneAgent into application containers, as described below.
Before you begin
If have access to your Kubernetes cluster, please see the instructions at How do I deploy Dynatrace OneAgent on Kubernetes?
What you'll need:
- Dynatrace environment credentials
Also, be sure to review the list of supported applications and versions.
If you don't have access to your Kubernetes cluster's underlying hosts, Dynatrace still enables you to selectively monitor the components of your applications—and the relationships between those components—by integrating OneAgent directly into each containerized application process.
Generate PaaS token
The first step is to get your environment ID and generate a PaaS token for your Dynatrace environment.
Login with your Dynatrace account.
Select Deploy Dynatrace from the navigation menu.
Click the Set up PaaS integration button.
Your environment ID appears in the Environment ID text box. You'll need this ID to link your Dynatrace account with your PaaS environment. Click Copy to copy the ID to the clipboard. You can do this at any time by revisiting this page.
To generate a PaaS token, click the Generate new token button. The PaaS token is essentially an API token that's used in combination with your environment ID to download Dynatrace OneAgent. As you'll see, there's also a default InstallerDownload token available that you can alternatively use. However, for security reasons, it's recommended that you create several discrete tokens for each environment you have.
Type in a meaningful name for your PaaS token. A meaningful token name might be the name of the PaaS platform you want to monitor (for example,
openshift). To view and manage your existing PaaS tokens, go to Settings -> Integration -> Platform as a Service.
Click Generate to create the PaaS token. The newly created PaaS token will appear in the list below. Click Copy to copy the generated token to the clipboard. You can do this at any time by revisiting this page and clicking Show token next to the relevant PaaS token.
Integrate OneAgent into Kubernetes application containers
The following steps explain how to integrate OneAgent into a binary build with a Dockerfile.
Before you begin, ensure that your application start command uses
CMD in exec form:
CMD [ "executable", "param1", "param2" ]
First, define variables with optional default values using
<environmentID> with your Dynatrace environment ID. If you’re using Dynatrace Managed, you need to provide your Dynatrace Server URL (
<token> with the PaaS token mentioned above.
Technology support is enabled via
include parameters. Valid options for
php. Including specific technology-support options, rather than support for all technology options, results in a smaller OneAgent package.
Dynatrace OneAgent supports the flavor
musl for Alpine Linux based environemnts. Valid options for
To integrate OneAgent and activate instrumentation of your application, add the following commands to your current Dockerfile.
ARG DT_API_URL="https://<environmentID>.live.dynatrace.com/api" ARG DT_API_TOKEN="<token>" ARG DT_ONEAGENT_OPTIONS="flavor=default&include=<technology1>&include=<technology2>" ENV DT_HOME="/opt/dynatrace/oneagent" RUN mkdir -p "$DT_HOME" && \ wget -O "$DT_HOME/oneagent.zip" "$DT_API_URL/v1/deployment/installer/agent/unix/paas/latest?Api-Token=$DT_API_TOKEN&$DT_ONEAGENT_OPTIONS" && \ unzip -d "$DT_HOME" "$DT_HOME/oneagent.zip" && \ rm "$DT_HOME/oneagent.zip" ENTRYPOINT [ "/bin/sh", "-c", "/opt/dynatrace/oneagent/dynatrace-agent64.sh" ]
Note: Please extend the
ENTRYPOINT command above with your application arguments as needed, for example:
ENTRYPOINT [ "/bin/sh", "-c", "/opt/dynatrace/oneagent/dynatrace-agent64.sh java -cp /app HelloWorld.Main" ]
Note: The commands above that use
unzip may fail if they aren't provided by the base image.
Note: For OneAgent v1.139 you can also use an optimized
ENTRYPOINT [ "/opt/dynatrace/oneagent/dynatrace-agent64.sh" ]
Build your application image
Build the Docker image from your Dockerfile to use it in your Kubernetes environment:
$ docker build -t yourapp .
Monitor your application image in different Dynatrace environments
If you move your application from development to staging or production stages, you'll likely want to continue monitoring an application container after it moves to a new Dynatrace environment.
Beginning with OneAgent v1.139, you can change the Dynatrace environment for the monitoring of your Kubernetes applications without rebuilding your application image. This is done by supplying your Dynatrace environment ID via
DT_TENANT and the tenant token via
DT_TENANTTOKEN with your application image run command.
You can retrieve
DT_TENANTTOKEN from the following REST endpoint. In return, you get a JSON object that includes the
Be sure to replace
<token> with the proper values mentioned above. If you’re using Dynatrace Managed, you need to provide your Dynatrace Server URL (
Update OneAgent for Kubernetes
Each time a new version of Dynatrace OneAgent becomes available, you must rebuild your applications’ Docker image. Following restart, your Kubernetes applications will be monitored with the latest version of OneAgent.
If you've specified a default OneAgent install version for new hosts and applications using OneAgent updates settings, your Kubernetes applications will be automatically monitored by the defined default version of Dynatrace OneAgent.