Deploy OneAgent on AWS Fargate and AWS App Runner

• Kubernetes version 1.20+
• Dynatrace version 1.231+

1. Create an AWS Fargate pod execution role and a Fargate profile for your cluster by following the instructions in Getting started with AWS Fargate using Amazon EKS.

2. optional If you want the Kubernetes scheduler to run OneAgent in Fargate, add the dynatrace namespace to your Fargate profile in the AWS console.

3. Create a Dynatrace namespace.

shellcopydownload
kubectl create namespace dynatrace

4. Install Dynatrace Operator.

shellcopydownload
kubectl apply -f https://github.com/Dynatrace/dynatrace-operator/releases/download/v0.4.2/kubernetes.yaml

5. Create the secret holding the API token for authentication to the Dynatrace cluster.

shellcopydownload
kubectl -n dynatrace create secret generic dynakube --from-literal="apiToken=API_TOKEN"

6. Save the DynaKube custom resource definition. Retrieve the applicationMonitoring.yaml file from the GitHub repository.

shellcopydownload
curl -o applicationMonitoring.yaml https://github.com/Dynatrace/dynatrace-operator/blob/v0.4.2/config/samples/applicationMonitoring.yaml

7. Adapt the values of the custom resource as follows:

• required Specify the spec.apiUrl parameter, which is the URL of your Dynatrace environment, for your SaaS, Managed, or ActiveGate instance.

• optional Configure namespace selectors by setting the spec.namespaceSelector parameter. Namespaces matching this selector will be monitored; the rest will be ignored.

  Note: If no namespaceSelector is specified, all namespaces except the ones starting with kube- or -openshift- will be monitored.

• optional Configure spec.oneAgent.applicationMonitoring.version using semantic versioning (major.minor.patch - example: 1.203.0). If no version is specified, the OneAgent defaults to the latest version available.

• optional Configure network zones by setting the spec.networkZone parameter to your network zone.
  See network zones for more information.

8. optional Configure the injection.
   You can configure the injection through Kubernetes annotations. For details, see Pod annotation list

9. Create the custom resource

shellcopydownload
kubectl apply -f applicationMonitoring.yaml

10. Deploy your applications.
    All deployed pods will then be monitored.

Note: By default, OneAgent logs are located in /opt/dynatrace/oneagent-paas/log inside the instrumented containers. For guidance on troubleshooting possible issues, see Troubleshoot deployment and connectivity errors on Kubernetes.

To install Dynatrace OneAgent at runtime, you must deploy your application using a task with two container definitions. One is for downloading and unzipping the OneAgent to a shared volume, the other is your application container, which must mount the same volume.

For the runtime injection, follow the steps below.

1. Go to Fargate Task Definition > Create New Task Definition > select Fargate > click Next Step.

2. Name the task, optionally set roles and sizes, then scroll down to Volumes > Add volume. Add a volume of type Bind Mount named oneagent.

Note: You must create a volume before creating container definitions in order to set the shared volume in each container.

3. Scroll up to Container Definition > choose Add container, and in the Standard subsection, add a container named install-oneagent, set the image to Alpine versions 3.8+ ("alpine:3"), and select the memory limits.

Note: There are two types of memory limits: soft and hard. ECS requires that you define the limit for at least one type of memory. We recommend using the default setting (soft limit of 128 MiBs), as it's less restrictive, but you can adjust it as needed.

4. Scroll to Environment and do the following:

• Uncheck the Essential parameter.
• In the Entry point field, enter /bin/sh,-c.
• In the Command field, enter ARCHIVE=$(mktemp) && wget -O $ARCHIVE "$DT_API_URL/v1/deployment/installer/agent/unix/paas/latest?Api-Token=$DT_PAAS_TOKEN&$DT_ONEAGENT_OPTIONS" && unzip -o -d /opt/dynatrace/oneagent $ARCHIVE && rm -f $ARCHIVE.

5. In the Environment variables subsection, define:

• DT_API_URL - this is the API URL for your Dynatrace environment.
  • For SaaS: https://<your-environment-id>.live.dynatrace.com/api
  • For Managed: https://<cluster>/e/<your-environment-id>/api
  • For ActiveGate: https://<your-active-gate-IP-or-hostname>:9999/e/<your-environment-id>/api.
• DT_ONEAGENT_OPTIONS- this is the flavor (valid options are default or musl for Alpine images) and the technology (code module).
  • Syntax for default is flavor=default&include=all.
  • Syntax for musl is flavor=musl&include=all.
• DT_PAAS_TOKEN - this is your PaaS token to download the OneAgent code modules.

6. Scroll to Storage and logging to define the mount point with the source volume oneagent and the container path /opt/dynatrace/oneagent.

7. Click Add to create the container definition.

8. Choose Add container again, this time to define your application, and complete the fields in the Standard subsection according to your application requirements.

9. Scroll to Environment, and in Environment variable, define LD_PRELOAD with the value /opt/dynatrace/oneagent/agent/lib64/liboneagentproc.so.

10. Scroll to Startup Dependency Ordering and enter the container name install-oneagent and the condition Complete.

11. Scroll to Storage and logging to define the mount point with the source volume oneagent and the container path /opt/dynatrace/oneagent.

12. Select Update to update your container definition.

13. Deploy the new version of your task definition on your ECS cluster.

Note:

• On the Logs tab for the install-oneagent container, you can see the code modules' ZIP file being downloaded by wget and being unzipped.
• On the Logs tab for your application workload container, you can see the code module being loaded by the process.

In the Dynatrace web UI, your Fargate application workload container will show up in the Hosts section. The instrumented process will show up in Processes as a typical Docker container.