Dynatrace monitors containerized applications on many platforms, including Kubernetes, Amazon ECS, Docker, and Cloud Foundry. On Kubernetes and Amazon ECS, you can also license your container workloads per container-hour, with Container Application Monitoring. This works the same for OneAgent and OpenTelemetry.
| Platform | Instrumentation | Container identity attributes | Setup guide |
|---|---|---|---|
| Kubernetes: EKS, AKS, GKE (including Autopilot), OpenShift, and other supported distributions | OneAgent in application monitoring mode, or OpenTelemetry | k8s.pod.uid, k8s.container.name | Kubernetes container workloads |
| Amazon ECS on AWS Fargate and Amazon EC2 | OneAgent code modules inside the task, or OpenTelemetry | aws.ecs.container.arn | Amazon ECS container workloads |
It works with every technology that OneAgent code modules support, and with any OpenTelemetry source that exports via OTLP.
On other platforms, or when OneAgent monitors the host (for example, full-stack on Kubernetes or the daemon service on ECS), containers are licensed with other models, such as Full-Stack Monitoring. See Other container platforms.
For rates, included volumes, counting rules, and cost examples, see Container Application Monitoring consumption.
A container is licensed per container-hour only if it's opted in and its telemetry carries the container identity attributes listed above.
builtin:billing.container-application-monitoring.optin opts in all eligible OneAgent containers. It's enabled by default for new customers. Alternatively, set the resource attribute dt.has_container_application_monitoring=true.dt.has_container_application_monitoring=true. The tenant-wide setting doesn't apply.Telemetry that isn't opted in, or lacks the attributes, falls back: OneAgent to GiB-hour licensing, and OpenTelemetry to Traces and Metrics - Ingest & Process.
On Kubernetes, a restarted container keeps its licensing identity and isn't counted twice. It gets a new identity only when its pod is recreated. On Amazon ECS, a restarted container keeps its identity as long as its container ARN stays the same. If it gets a new ARN, for example because its task is replaced, it's counted as a new container.