AppD Archive

Can't get data using docker

CommunityUser
Splunk Employee
Splunk Employee

Hello everybody!

I'm trying to use appdynamics in my docker container. I use node 4.4.0 and appdynamics agent version 4.1.10 with alpine docker image. When I use my app out of container, appdynamics recognize my app, but not inside.

process-0.json log from docker

{ 
"appName": "xxxxxxxx", 
"tierName": "xxxxxxxxx", 
"nodeName": "process-0", 
"controllerHost": "xxxxxxxxxxxxxxxxxxx", 
"controllerPort": 443, 
"sslEnabled": true, 
"accountName": "xxxxxxxxxxxxxx", 
"accountAccessKey": "xxxxxxxxxxxxxxx", 
"logs": { 
"out": [ 
{ 
"msg": "agent.tmpDir = \"/tmp/appd/cca4cd7358baae2927a31d30602e9bdb\"", 
"t": "14-06-2016 14:38:35.852" 
}, 
{ 
"msg": "agent.proxyCtrlDir = \"/tmp/appd/cca4cd7358baae2927a31d30602e9bdb/proxy/c\"", 
"t": "14-06-2016 14:38:35.854" 
}, 
{ 
"msg": "Loaded native extention.", 
"t": "14-06-2016 14:38:35.857" 
}, 
{ 
"msg": "launching proxy from master node 0", 
"t": "14-06-2016 14:38:35.859" 
}, 
{
"msg": "ProcessScanner - snapshotCountResetPeriodMS: 60000", 
"t": "14-06-2016 14:38:35.876" 
}, 
{ 
"msg": "ProcessScanner - autoSnapshotDurationSeconds: 10", 
"t": "14-06-2016 14:38:35.876" 
}, 
{ 
"msg": "found cluster module", 
"t": "14-06-2016 14:38:35.886" 
}, 
{ 
"msg": "found fs module", 
"t": "14-06-2016 14:38:35.887" 
}, 
{ 
"msg": "found http module", 
"t": "14-06-2016 14:38:35.895" 
}, 
{ 
"msg": "found https module", 
"t": "14-06-2016 14:38:35.902" 
}, 
{ 
"msg": "found mongodb module", 
"t": "14-06-2016 14:38:36.055" 
},
{ 
"msg": "found net module", 
"t": "14-06-2016 14:38:36.055" 
}, 
{ 
"msg": "proxyArgs = [\n \"-d\",\n \"/install/node_modules/appdynamics/node_modules/appdynamics-proxy/proxy\",\n
"t": "14-06-2016 14:38:37.355" 
}, 
{ 
"msg": "cmdLine = /install/node_modules/appdynamics/node_modules/appdynamics-proxy/proxy/runProxy -d /install/no
"t": "14-06-2016 14:38:37.355" 
}, 
{ 
"msg": "Proxy logging to: /tmp/appd/cca4cd7358baae2927a31d30602e9bdb/proxy/l", 
"t": "14-06-2016 14:38:37.360" 
}, 
{ 
"msg": "Proxy spawned!", 
"t": "14-06-2016 14:38:37.360" 
}, 
{ 
"msg": "starting control socket..", 
"t": "14-06-2016 14:38:40.869" 
} 
], 
"err": [] 
} 
}

UPDATE:

With debug mode I have it too

2016-07-14T18:44:58.448684678Z appdynamics v4.1.10.0 (14-06-2016 18:44:58.448): Proxy spawned!
2016-07-14T18:45:08.439100696Z appdynamics v4.1.10.0 (14-06-2016 18:45:08.438): attempting to re-launch proxy...
2016-07-14T18:45:08.439155589Z appdynamics v4.1.10.0 (14-06-2016 18:45:08.438): launching proxy from master node 0
2016-07-14T18:45:08.441094864Z appdynamics v4.1.10.0 (14-06-2016 18:45:08.438): ERROR: no response on control socket
0 Karma

Angela_Lang
Path Finder

Hello,

Below are some resources that might help.

At a high level, best practice is to run the stand alone machine agent on the Docker host only, and deploy the Docker extension in that machine agent to collect metrics about the containers. If you run the machine agent inside a container, you will only see the processes and memory owned by the container, plus the virtual network I/f and disk drivers for that containers. You cannot see OS-level stats on the docker host, because of container isolation.  The memory/cpu reported by the machine agent in the container will usually be steady in the 90% range because of the way resources are managed by docker.

Technical Webinar on AppDynamics and Docker:

https://community.appdynamics.com/t5/Tech-Webinars/AppDynamics-and-Docker-Tech-Webinar-and-Office-Ho...

Docker Monitoring Extension:

https://www.appdynamics.com/community/exchange/extension/docker-monitoring-extension/

Article - Complete Visibility into Docker containers with AppDynamics:

https://blog.appdynamics.com/devops/complete-visibility-into-docker-environment-with-appdynamics/

I hope this helps!

0 Karma
Get Updates on the Splunk Community!

See just what you’ve been missing | Observability tracks at Splunk University

Looking to sharpen your observability skills so you can better understand how to collect and analyze data from ...

Weezer at .conf25? Say it ain’t so!

Hello Splunkers, The countdown to .conf25 is on-and we've just turned up the volume! We're thrilled to ...

How SC4S Makes Suricata Logs Ingestion Simple

Network security monitoring has become increasingly critical for organizations of all sizes. Splunk has ...