Migrate from cloud native full stack to application monitoring mode

Dynatrace Operator version 1.0.0+

This guide describes the steps required to migrate your Dynatrace deployment from cloud native full stack to the application monitoring mode.

Advantages

To only monitor selected applications on Kubernetes, application monitoring offers a flexible approach with the following benefits:

  • The application monitoring mode, similar to the cloud native full stack mode, prevents race conditions that can occur when OneAgent DaemonSet pods and monitored application pods start simultaneously.
  • By leveraging Kubernetes concepts such as admission webhooks and CSI driver for Code Module injection, application monitoring mode reduces the required privileges for OneAgent.

Considerations and implications

  • When switching to application monitoring, previously deployed OneAgents will get deactivated and deep monitoring of applications will stop. Consequently, restarting all application pods that require deep monitoring becomes mandatory. Restarting these pods ensures that applications are reinjected, allowing deep monitoring to resume.
  • In application monitoring mode, container monitoring rules are ignored. Instead, label selectors should be employed to precisely manage OneAgent injection.
  • Log monitoring requires additional setup.

Migrate to application monitoring mode

This section provides all the information needed to perform the migration from cloud native full stack to application monitoring mode.

  1. Reconfigure (existing) DynaKube for application monitoring mode:

    The following side-by-side comparison outlines how to reconfigure a DynaKube CR from cloud native full stack to application monitoring:

    apiVersion: dynatrace.com/v1beta2
    kind: DynaKube
    metadata:
      name: dynakube
      namespace: dynatrace
    spec:
      apiUrl: https://<environment-id>.live.dynatrace.com/api
    

      networkZone: <network-zone>
    

      oneAgent:
        cloudNativeFullStack:
          args:
            - "--set-host-group=<host-group>"
    

    activeGate:
        capabilities:
          - routing
          - kubernetes-monitoring
          - dynatrace-api

    For further information on how to configure DynaKube for application monitoring mode, visit the deployment guide or DynaKube parameters. Alternatively, download the DynaKube custom resource sample for application monitoring from GitHub and adapt the DynaKube custom resource according to your requirements.

  2. Apply the DynaKube custom resource:

    Run the command below to apply the DynaKube custom resource. A validation webhook will provide helpful error messages if there's a problem.

    kubectl apply -f dynakube.yaml

    This action will lead to the removal of OneAgents in cloud native full stack mode and subsequently result in the termination of deep monitoring for application pods shortly thereafter.

  3. Restart application workloads:

    Restart all application workloads promptly to trigger OneAgent injection and enable deep monitoring minimizing monitoring outages.

Changes in Kubernetes resources

The migration impacts several Kubernetes resources, altering their functions or introducing new components to support the application monitoring monitoring mode. Key changes include:

Component

Cloud native full stack

Application monitoring

Dynatrace OneAgent

  • Deployed as a DaemonSet
  • Collect host metrics on nodes
  • Not present

Dynatrace Webhook Server

  • Validates DynaKube definitions
  • Inject code modules into application pods by modifying pod definitions
  • Validates DynaKube definitions
  • Inject code modules into application pods by modifying pod definitions

required

  • Deployed as a DaemonSet
  • Provides volume storage for OneAgents
  • Manages and provides code modules used for pod injection and optimizes storage consumption

optional

  • Deployed as a DaemonSet
  • Manages and provides code modules used for pod injection and optimizes storage consumption