Showing results for 
Show  only  | Search instead for 
Did you mean: 

Unable to monitor Tomcat



I am setting up Dynatrace to monitor 3 docker containers running on a VM.

So the steps Ive done till now are to run the command on my docker host.

docker run -d --restart=unless-stopped --privileged=true --pid=host --net=host --ipc=host -v /:/mnt/root -e ONEAGENT_INSTALLER_SCRIPT_URL="https://<URL_TO_MY_DYNATRACE_INSTANCE>/e/bf04f8bb-444b-41b2-a0fb-1b58f3123a68/api/v1/deployment/installer/agent/unix/default/latest?Api-Token=XbPpcnr9TnyQqqFppJhgO&arch=x86&flavor=default" dynatrace/oneagent:1.22.1000 APP_LOG_CONTENT_ACCESS=1

I even used the latest image.

The 3 containers running are Tomcat, Nginx and MySQL.

The problem I am getting is that the services Tomcat and Nginx are not being monitored and Im getting the Warning "This process must be restarted"
Ive done a docker-compose restart as well as manually restarting the docker containers but the Warning does not go away. Even restarted the VM.

I even downloaded a generic tomcat docker image from DockerHub, ran that and that too is giving the same Warning.

Im not sure what Ive missed ? What would be the best way to troubleshoot this ?

I even stopped the docker container and installed OneAgent via script but the issue is the same.


DynaMight Guru
DynaMight Guru

Hello @Jay S.

I have never been done Docker Instrumentation but while reading the documentation I found that there are some limitations on both platforms (Linux and Windows) and also there are specific supported technologies.

Just have a look on the below links in case something is missing or unsupported technology used.



Could have something to do with the start order? Oneagent needs to be there before you start the Tomcat or Nginx process.

You are passing the install-url, so it looks like the oneagent is downloaded and installed at startup of the container. While the tomcat is already in the image and probably started automatically.
It might just be the trick to install the oneagent in the image as well at build time. Or use the initContainer approach.

Featured Posts