Click the Start a free trial link to start a 15-day SaaS trial of our product and join our community as a trial user. If you are an existing customer do not start a free trial.
AppDynamics customers and established members should click the sign in button to authenticate.
We are having issues deploying app agent on our AWS environment.
We can deploy the agent and monitor the application on our local machine. However, when deploying our application to an AWS environment we fail to see data coming from the environment and see errors in the AppD logs.
Any assistance on this would be highly appreciated.
What errors do you see in the agent logs?
We have many customers monitoring applications deployed in EC2, so there is no fundamental problem with what you are doing.
To ‘add a little color’ to the issue Sayed is referring to:
We’re currently evaluating AppD’s Node.js agent for our containerized application. After building our application’s docker image and running the container on our workstations, the application successfully connects to our SaaS controller and reports application metrics.
When the same container is deployed to our Kubernetes cluster(hosted on AWS EC2/VPC), the container runs with no issue from the perspective of the application - however we do not see data being reported to the Controller console. We’ve confirmed SaaS controller connectivity from the application container using curl(curl -I “https://our.saas.fqdn”) and recieve a 200 response.
We're using no other AppD agents other than the application agent for Node.js 8.9.1.
I've attached the agent log file if it's of any help.
It looks like the agent is unable to launch its communcation proxy:
[2018-03-13 14:12:31.062] [INFO] default - Proxy logging to: /tmp/appd/709d8f016ec1eba1a412d004d957647e/proxy/l
[2018-03-13 14:12:31.062] [INFO] default - Proxy spawned!
[2018-03-13 14:12:40.855] [ERROR] default - no response on control socket
[2018-03-13 14:12:40.888] [ERROR] default - unable to contact proxy
Are there any proxy logs? If so, could you post them? If not, could you collect debug logs from the agent and post these?
I see nothing obviously wrong in these logs. The log from the proxy instance servicing the node process would be useful too.
I suggest the best way to take this forward is via a support ticket; are you able to open one and attach all the logs?