Yes, Kubernetes workloads and pods are monitored differently compared to traditional OneAgent-monitored processes. When Dynatrace is deployed into Kubernetes using the Dynatrace Operator, the OneAgent automatically injects itself into each pod at runtime. This means each container is monitored independently and is shown in Dynatrace as a container entity , not as a traditional process.

This container-based visibility is designed to suit the dynamic and short-lived nature of Kubernetes environments. Traditional OneAgent monitoring associates metrics and topology with processes and hosts, but in Kubernetes, the emphasis shifts toward containers, pods, and workloads. This shift allows Dynatrace to provide accurate and timely data on what’s really happening inside containerized apps, aligned with Kubernetes-native objects and metrics.

Other answer options either misstate the behavior (e.g., no service data or requiring OpenTelemetry) or oversimplify the relationship between traditional and Kubernetes monitoring (e.g., "same general information"), making Option E the only correct and fully accurate one.