Java Agent Docker Container Install as Sidecar vs Inside Application Container

[Anonymous]

Hi,

Presently we are installing the Java agent in the same container as the application. We had some application issues and the engineering team became suspect that the Java agent performance may be affecting performance. I know this is unlikely, but one never truly knows in the software world. Things that aren't supposed to happen, sometimes do.

I'd like to know how, if possible, to install that Java agent as a sideloaded (sidecar) container so there is some resource isolation from the actual application container.

I haven't found any documentation on that, but might be overlooking it.

We are using AWS ECS and Docker images. 

1. Is there a sidecar Docker image for the Java agent?

2. What specifical configuration is required? Ports, directory paths, etc.?

3. Is this documented somewhere?

[Atyuha.Pal]

Hi  christopher,

There is no particular guidelines for installing java agent on the docker. They will still be attached to their respective application server as always.

Thanks,

Atyuha

[Vijay.Kakarla]

Hi,

We are also in the same boat. Looking for some documentation.

[Stephen.Davies]

Hey,

Here's a blog post talking about this:

https://www.appdynamics.com/blog/engineering/how-to-instrument-docker-containers-with-appdynamics/

They mention specifically about sidecar deployments