Try it free

Monitor container workloads

  • Latest Dynatrace
  • Overview
  • 5-min read
  • Published Nov 15, 2026

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.

Where container-hour licensing is available

PlatformInstrumentationContainer identity attributesSetup guide
Kubernetes: EKS, AKS, GKE (including Autopilot), OpenShift, and other supported distributionsOneAgent in application monitoring mode, or OpenTelemetryk8s.pod.uid, k8s.container.nameKubernetes container workloads
Amazon ECS on AWS Fargate and Amazon EC2OneAgent code modules inside the task, or OpenTelemetryaws.ecs.container.arnAmazon 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.

How container-hour licensing works

  • Each monitored container counts as one container-hour per hour, regardless of its size.
  • Each container adds an included volume of traces and metrics, shared by OneAgent and OpenTelemetry. Volume above it is licensed as Traces - Ingest & Process and Metrics - Ingest & Process.
  • For OneAgent, Adaptive Traffic Management keeps trace data within the included volume. For OpenTelemetry, configure sampling yourself to stay within it.

For rates, included volumes, counting rules, and cost examples, see Container Application Monitoring consumption.

Opt in your containers

A container is licensed per container-hour only if it's opted in and its telemetry carries the container identity attributes listed above.

  • OneAgent OneAgent version 1.345+: The tenant-wide setting 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.
  • OpenTelemetry: Always set the resource attribute 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.

Container restarts

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.

Limitations

  • Not on hosts monitored by OneAgent. These hosts are already licensed through host monitoring, so opting their containers in would license them twice.
  • Profiling isn't included. Profiling and thread analysis aren't part of Container Application Monitoring. They're available with Full-Stack Monitoring.
  • Code Monitoring is licensed separately, as Code Monitoring container-hours.
  • Wait one week after moving to DPS. If your environment just migrated from Dynatrace classic licensing, the trace volume migration must finish first.

Learn more

  • Set up: Kubernetes setup with Dynatrace Operator, OTLP exporter auto-configuration, Monitor AWS Fargate
  • Migrate: from GiB-hour licensing, from classic full-stack, from cloud-native full-stack
  • Licensing: Container Application Monitoring consumption, Kubernetes Platform Monitoring, OpenTelemetry licensing, cost allocation