Enable Auto-Instrumentation for the Cluster Agent

To set up the Cluster Agent feature:

  1. Remove any deleted pods from the Tiers & Nodes Controller Dashboard. Then, re-create the cluster-agent-secret that was created in Install the Cluster Agent to include api-user: 
    kubectl -n appdynamics delete secret cluster-agent-secret
kubectl -n appdynamics create secret generic cluster-agent-secret --from-literal=controller-key=<access-key> --from-literal=api-user="<username>@<customer>:<password>"
    Note: Set the api-user value to a local user from the Controller with the Server Monitoring Administrator role. Cluster Agent uses the api-user to mark the associated node in the Controller as historical on pod deletion.
  2. Add auto-instrumentation configuration to the cluster-agent.yaml or the Helm values.yaml file. The configuration determines which Deployments, DeploymentConfigs and StatefulSets workloads to target for auto-instrumentation and which agent types and versions to use. See Auto-Instrumentation Configuration.
  3. After you save the configuration, apply or upgrade the Cluster Agent deployment. The related pods and containers restart based on the deployment rollout strategy associated with the applications.To validate and troubleshoot auto-instrumentation, see
    Kubernetes CLI
    kubectl apply -f cluster-agent.yaml
    Helm Chart
    helm upgrade -f ./ca1-values.yaml "<my-cluster-agent-helm-release>" appdynamics-charts/cluster-agent --namespace appdynamics

    To validate and troubleshoot auto-instrumentation, see Validate the Cluster Agent Installation.

Note:

  • If a workload does not match the properties defined in instrumentationRules, then auto-instrumentation is not enabled.

  • If an auto-instrumentation property is not defined as a default, or in instrumentationRules, then the Cluster Agent uses the corresponding default value specified in Auto-Instrumentation Configuration. If there are no corresponding default values, then auto-instrumentation is not enabled.