Classic Full-Stack monitoring

Classic Full-Stack monitoring integrates host and application monitoring for Kubernetes environments. Instrumented pods maintain their relationship with hosts, enabling the collection of host metrics.

See .spec.oneAgent.classicFullStack section of DynaKube for additional information.

Capabilities

  • Instrumented pods maintain their taxonomic relationship with hosts and host metrics. OneAgent complements code modules with OOM detection, disk and storage monitoring, network monitoring, and more.
  • This all-in-one approach includes Kubernetes cluster monitoring, distributed tracing, fault domain isolation, and deep code-level insights using a single deployment configuration across your clusters.

Limitations

There’s a startup dependency between the container where OneAgent is deployed and the application container to be instrumented (for example, containers with deep process monitoring enabled). The OneAgent container must be started, and the oneagenthelper process must be running before the application container is launched to ensure proper instrumentation.

Deployed resources

Dynatrace Operator components

The following components are deployed via Helm/Manifests as part of the core installation. For more information, go to their respective sections:

  • Dynatrace Operator manages the automated rollout, configuration, and lifecycle of Dynatrace components in your Kubernetes environment.
  • Dynatrace Operator webhook validates DynaKube definitions, converts definitions with older API versions, and injects configurations into pods.

Operator-managed components

The following components are deployed by applying a DynaKube with full-stack observability:

classic-full-stack

Classic full-stack injection requires write access from the OneAgent pod to the Kubernetes node file system to detect and inject into newly deployed containers.