Application observability focuses on monitoring application-level metrics by injecting code modules into application pods. This mode offers multiple injection strategies (automatic, runtime, and build-time) to collect application-specific metrics. For infrastructure-level insights, combine it with Kubernetes platform monitoring.
See .spec.oneAgent.applicationMonitoring
section of DynaKube for additional information.
You can use the automatic injection strategy for application pods. Dynatrace injects code modules into pods using the Kubernetes admission controller. This approach allows you to collect application-specific metrics and monitor container-level metrics.
When deployed in application monitoring, Dynatrace code modules monitor processes within the container, including disk, CPU, and networking metrics. Host metrics are not monitored. Without Kubernetes Platform Monitoring, topology is limited to pods and containers.
The following components are deployed via Helm/Manifests as part of the core installation. For more information, go to their respective sections:
The following component is deployed by applying a DynaKube with Application observability:
You can use the application monitoring for application pods. You don't install OneAgent pods and can't collect host metrics from Kubernetes nodes.
Because Dynatrace Operator is not involved, no automatic injection, configuration, or enrichment occurs. You need to manually adjust your Kubernetes workloads.
You can use the application monitoring for application pods. You don't install OneAgent pods and can't collect host metrics from Kubernetes nodes.
Without Dynatrace Operator, there is no automatic injection, configuration, or enrichment. You need to manually adapt your build process.