Once you have deployed the Python application with the Python Agent and generated load on the application, the application should appear in the AppDynamics Controller based on the configured application, tier, and node names. To troubleshoot communication issues between the agent and the proxy, or proxy and Controller log on to the application and proxy containers. Note that logs will not appear until the application process receives requests.

# check that the app and proxy containers are running
kubectl -n <app ns> get pods
NAME                                 READY   STATUS    RESTARTS   AGE
mypython-app-7687956c77-q5z85        2/2     Running   0          40s
# if both containers aren't running, check events regarding image pulls, etc
kubectl -n <app ns> get events
# check the Python Agent logs in the application container for issues communicating with the proxy running in the sidecar
kubectl -n <app ns> exec -it <pod name> -c <app container name> /bin/bash
cd /tmp/appd/logs
cat <app-node names>.log
# check the proxy logs for issues communicating with the AppDynamics Controller
kubectl -n <app ns> exec -it <pod name> -c proxy /bin/bash
cd /tmp/appd/logs/<app folder>
cat agent.<timestamp>.log