Troubleshoot a Cluster Agent Not Reporting to the Controller

If after installing the Cluster Agent the Cluster Dashboard does not appear in the Controller, it could be the result of a connectivity issue with the Controller.

  1. Verify that a Server Visibility license is available. The Cluster Agent requires an available Server Visibility license to register successfully. See Cluster Agent Requirements and Supported Environments. From the Controller UI, check that a license is available under Administration/License/Account Usage.
  2. Review the Cluster Agent events. If the Cluster Agent or Cluster Agent Operator fails to start, then review the events in the appdynamics namespace: 
    kubectl -n appdynamics get events
# to sort by most recent events:
kubectl -n appdynamics get events --sort-by='.lastTimestamp'
    You can review the Cluster Agent pod specification for additional events:
    kubectl -n appdynamics get pod <cluster-agent-pod> -o yaml
  3. Review the Cluster Agent logs for errors regarding Controller communication. Open a command-line prompt and enter: 
    kubectl -n appdynamics logs <cluster-agent-pod-name>
  4. Verify the Cluster Agent configuration. The Cluster Agent checks for configuration changes once a minute. To verify that your configurations have been applied and that the Cluster Agent is using the new values, open a command-line prompt and enter: 
    kubectl -n appdynamics describe cm cluster-agent-mon cluster-agent-log cluster-agent-config
  5. Verify that the latest Cluster Agent is installed. If you are upgrading the Cluster Agent from a previous version, then the previous Operator YAML or image may not be compatible. You must reinstall the Cluster Agent Operator and Cluster Agent using the procedure described in Upgrade the Cluster Agent.