Splunk AppDynamics

Docker monitoring doesn't work

CommunityUser
Splunk Employee
Splunk Employee

Hi folks,

I've installed AppDynamics machine agent in a docker container on one of our docker hosts:

docker run -d --name sys_appd_machine_agent \
    -v /:/hostroot:ro \
    -v /var/run/docker.sock:/var/run/docker.sock \
    --restart always \
    -m 256m \
    -e "JAVA_OPTS=-Xms64m -Xmx256m" \
    -e "APPD_HOST=hostname" \
    -e "APPD_PORT=8090" \
    -e "APPD_ACCOUNT_NAME=username" \
    -e "APPD_ACCESS_KEY=key-key-key" \
    -e "APPD_SSL_ENABLED=false" \
    appd-machine-agent:4.5.5.1784

Following exception was thrown for each of the container on the host:

16:51:32,762  WARN [Docker-Monitoring-0] DockerRegistrationTask - Error registering containerId : a5fefcc9cd6d8e1ca24b0a09ac2e15bedebfdb3e38d6f6eb98359ee686e48be3  with error {}
com.appdynamics.voltron.rest.utils.RestException: The requested object was not found. Please make sure you are attempting to access visible data. Another user may have deleted the data. This may also be a problem with the server. If the problem persists, please contact support. (404 - MISSING_ERROR)
	* Additional Info:Unable to find matching machine instance with hostId: a5fefcc9cd6d. Container registration without application app agent is not supported yet.
	* Server stack trace:
		Hidden
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at com.fasterxml.jackson.databind.introspect.AnnotatedConstructor.call(AnnotatedConstructor.java:119)
	at com.fasterxml.jackson.databind.deser.std.StdValueInstantiator.createUsingDefault(StdValueInstantiator.java:269)
	at com.fasterxml.jackson.databind.deser.std.ThrowableDeserializer.deserializeFromObject(ThrowableDeserializer.java:145)
	at com.fasterxml.jackson.databind.deser.BeanDeserializer.deserialize(BeanDeserializer.java:148)
	at com.fasterxml.jackson.databind.ObjectMapper._readMapAndClose(ObjectMapper.java:3814)
	at com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:2858)
	at com.appdynamics.voltron.rest.client.VoltronErrorDecoder.decode(VoltronErrorDecoder.java:50)
	at feign.SynchronousMethodHandler.executeAndDecode(SynchronousMethodHandler.java:134)
	at feign.SynchronousMethodHandler.invoke(SynchronousMethodHandler.java:76)
	at feign.ReflectiveFeign$FeignInvocationHandler.invoke(ReflectiveFeign.java:103)
	at com.sun.proxy.$Proxy89.registerMachine(Unknown Source)
	at com.appdynamics.sim.agent.extensions.docker.DockerRegistrationTask.registerLightSystemAgent(DockerRegistrationTask.java:192)
	at com.appdynamics.sim.agent.extensions.docker.DockerRegistrationTask.call(DockerRegistrationTask.java:256)
	at com.appdynamics.sim.agent.extensions.docker.DockerRegistrationTask.call(DockerRegistrationTask.java:56)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)

As expected docker container metrics are emtpy in AppDynamics container for the host.

What is wrong there?

Kind regards

Artem

Labels (1)
0 Karma
1 Solution

CommunityUser
Splunk Employee
Splunk Employee

Hi @Anonymous

The error message states :

Container registration without application app agent is not supported yet 

It appears to us that you have not installed an app agent in your environment. You need to install an app agent inside each container you want to monitor.  Please see the Container Monitoring documentation for details.

View solution in original post

CommunityUser
Splunk Employee
Splunk Employee

Hi @Anonymous

The error message states :

Container registration without application app agent is not supported yet 

It appears to us that you have not installed an app agent in your environment. You need to install an app agent inside each container you want to monitor.  Please see the Container Monitoring documentation for details.

Get Updates on the Splunk Community!

Brains, Bytes, and Boston: Learn from the Best at .conf25

When you think of Boston, you might picture colonial charm, world-class universities, or even the crack of a ...

Splunk AppDynamics Agents Webinar Series

Mark your calendars! On June 24th at 12PM PST, we’re going live with the second session of our Splunk ...

SplunkTrust Application Period is Officially OPEN!

It's that time, folks! The application/nomination period for the 2025 SplunkTrust is officially open! If you ...