Not a customer? Click the 'Start a free trial' link to begin a 30-day SaaS trial of our product and to join our community.
Existing Cisco AppDynamics customers should click the 'Sign In' button to authenticate to access the community
02-28-2018 04:29 AM - last edited on 01-15-2020 12:29 PM by Ryan.Paredez
Hi,
Currently, we have multiple docker based containers running in AWS ECS and we are trying to install appdynamics agents in ECS.
How do we achieve this?
Solved! Go to Solution.
03-01-2018 09:20 PM
Hi Liana,
Can you give some information on which agent you are trying to install?
Will guide you accordingly.
Thanks and Regards,
Sajna Sreenivasan
11-01-2018 11:05 AM
I am also looking for this information.
I'm already deploying the java application agent in each of my docker containers running in ECS.
However what I am trying to do specifically is run the machine agent as a docker container as discussed in these resources:
https://blog.appdynamics.com/product/amazon-ecs-or-eks-appdynamics-supports-both/
https://docs.appdynamics.com/display/AWS/AWS+and+AppDynamics+APM
When we ultimately start to run the container via the ECS task, we get the following error:
Could not start up the machine agent due to: Failed to get a response from /info using a GET request. The error encountered is: javax.xml.ws.WebServiceException: Cannot connect to Docker. The unix socket file /var/run/docker.sock does not exist. Please provide a valid file to access.
Details:
Container = server agent image (with integrated docker visibility):
docker pull store/appdynamics/machine:4.4
The following environment variables are getting set:
APPDYNAMICS_AGENT_APPLICATION_NAME = xxx
APPDYNANNICS_SIM_ENABLED = true
APPDYNAMICS_DOCKER_ENABLED = true
APPDYNAMICS_AGENT_NODE_NAME = xxx
APPDYNAMICS_AGENT_TIER_NAME = xxx
APPDYNAMICS_CONTROLLER_HOST_NAME = xxx
APPDYNAMICS_AGENT_ACCOUNT_NAME = xxx
APPDYNAMICS_AGENT_ACCOUNT_ACCESS_KEY = xxx
APPDYNAMICS_CONTROLLER_SSL_ENABLED = xxx
APPDYNAMICS_CONTROLLER_PORT = xxx
The DAEMON strategy is being used in ECS for the task.
Note – I did not configure any ports for the appdynamics agent. It did not appear per documentation this was required – nor could I tell what port needed to be mapped in the ECS task, so none was specified.
02-26-2019 06:15 PM
Was this issue resolved? If yes, how?
Thanks, Prateek
02-27-2019 08:35 AM - edited 02-27-2019 08:38 AM
Hello Prateek
After working with appDynamics support, the missing piece for us was to run the machine agent container using the DAEMON strategy in ECS:
Once we did this, we got past the errors and were able to start the container.
Additionally, we had to add the following mounts to the task definition
/:/hostroot:ro
/var/run/docker.sock:/var/run/docker.sock
12-09-2019 07:14 AM
Hi,
It will be really helpful, if you can share me the documentation on how to enable appdynamics monitoring for java app hosted on AWS ECS Fargate?
01-14-2020 10:35 PM
Hi Experts,
We have aws ecs on ec2. We are trying to deploy java agent on it. We have created new task definition with app-agent tomcat image. Do we need to create service of this task ? or we have to add this task in every service that we want monitor There is nothing mentioned in the blog after creation of task definition.
We have 15 services and 5 containers running.
Please help us.
Regards,
Sagar
01-28-2020 04:51 PM
01-29-2020 10:07 AM
Hi,
How would you configure machine Agent for a docker container running on AWS ECS Fargate ? The documentation is not very clear about how to do that.
Thanks
VVS
06-05-2024 03:57 AM
Good day @Venkata.Vadlamani hope you well,
Did you ever manage to get the monitoring right with Fargate?
I need to install the same on containers and also have a java and .net agents.
Please adviae?
regards.
Shane.
Thank you! Your submission has been received!
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form