Discussion Feed

Hello,    we are using a standalone machine agent to monitor a java application which is deployed in a Docker container. The machine agent is installed in a standalone container.   Our Dockerfile, where the directory ./AppServerAgent contains the machine agent:   FROM openjdk WORKDIR /app ENV APPDYNAMICS_AGENT_APPLICATION_NAME=petclinic ENV APPDYNAMICS_AGENT_TIER_NAME=petclinic-tier ENV APPDYNAMICS_AGENT_ACCOUNT_NAME=customer1 ENV APPDYNAMICS_AGENT_ACCOUNT_ACCESS_KEY=41130855-4203-471e-a836-3d241c9e8794 ENV APPDYNAMICS_CONTROLLER_HOST_NAME=ec2-3-122-240-100.eu-central-1.compute.amazonaws.com ENV APPDYNAMICS_CONTROLLER_PORT=8090 ENV APPDYNAMICS_CONTROLLER_SSL_ENABLED=false ENV APPDYNAMICS_AGENT_NODE_NAME=petclinic-node COPY ./AppServerAgent/ /opt/appdynamics/ COPY ./target ./target CMD ["java", "-javaagent:/opt/appdynamics/javaagent.jar", "-jar", "target/spring-petclinic-2.4.2.jar"] We use the official docker image of AppDynamics from the Docker Hub:  docker pull store/appdynamics/machine:4.5 And run the container with the following parameters referring to our on-prem AppD Controller: docker run -d \ -e APPDYNAMICS_CONTROLLER_HOST_NAME=ec2-3-122-240-100.eu-central-1.compute.amazonaws.com \ -e APPDYNAMICS_CONTROLLER_PORT=8090 \ -e APPDYNAMICS_CONTROLLER_SSL_ENABLED=false \ -e APPDYNAMICS_AGENT_ACCOUNT_NAME=customer1 \ -e APPDYNAMICS_AGENT_ACCOUNT_ACCESS_KEY=41130855-4203-471e-a836-3d241c9e8794 \ -e MACHINE_AGENT_PROPERTIES="-Dappdynamics.sim.enabled=true -Dappdynamics.docker.enabled=true" \ -v /proc:/hostroot/proc:ro -v /sys:/hostroot/sys:ro -v /etc:/hostroot/etc:ro -v /var/run/docker.sock:/var/run/docker.sock \ appdynamics/machine:4.5     Although the application is instrumented successfully, we can't view any Container.     We have enabled Server and Docker Visibility  and our License is also fine .    What are we missing? Thanks in advance and have a nice day! ... View more

I want to set up an on-prem AppD Platform according to this tutorial: https://github.com/sherifadel90/AppDynamicsPoVReadyLab (see Steps 1-3)   After unzipping and installing the  Enterprise Console - 64-bit Linux(sh) on my AWS instance   sudo su ./platform-setup-x64-linux-20.x.x.x.sh with inputing the below I accept the agreement: 1 Where should AppDynamics Enterprise Console be installed?: /usr/local/appdynamics/platform Database Root User Password: AppD123 Database Port: 3377 (default) Enterprise Console Database Password: AppD123 Enable Https Connection: n Enterprise Console Host Name: In case of AWS, Enter the public DNS name of the lab EC2 instance Enterprise Console Port: 9191 (default) Enterprise Console Root User Name: admin (default) Enterprise Console Root User Password: AppD123 I get the message that the installation succeeded. Setup has finished installing AppDynamics Enterprise Console on your computer. To install and manage your AppDynamics Platform, use the Enterprise Console CLI from /usr/local/appdynamics/platform/platform-admin/bin directory. Finishing installation ...   When calling my Enterprise Console through my web browser via ec2-52-59-205-162.eu-central-1.compute.amazonaws.com:9191  I get no response, although my service is running on port 9191   Does anyone have any idea how to get the Enterprise Controller properly started? All inbound ports on my AWS instance are open. So that's not an issue.   Thank you so much!     I am running a  m5.xlarge instace with 4 CPUs, 16 GB RAM and 100 GB storage. Os: Ubuntu 18.04. Openjdk version: 1.8.0_282   ... View more