Splunk AppDynamics

AppDynamics for Docker Swarm

Ravi_Verma
Engager

I am trying to test AppDyanmics against ELK and seeking some help in getting correct details - Please can someone help.

We are running docker-compose which creates 10 containers on 4 workers which are managed by 2 managers. All these containers are having one jvm running in it.

  • How can I use Appdynamics for Docker Swarm (there is a broken link in documentations and only available links are for K8S & OpenShift - I know docker is moving away from Swarm but need to existing env ?
  • How can I define my docker containers to use Node name (where the containers gets created by docker-compose) as container’ hostname - so that we can utilise only one machine agent and monitor all the containers running on that machine/node?
  • Can we just use machine agent to get containers details (running on that machine) which should tell containers statistics and logs details Or do we need to install app agents in the containers- If yes then please could you suggest how to proceed 

Thanks in advance

Labels (1)
Tags (2)
0 Karma
1 Solution

Ravi_Verma
Engager

I have found out that we need to install app-agents inside the containers.

It can not work only with machine-agent installation/configuration, you need to use app-agents as well.

I have referred below articles which has helped me to run appdynamics for my docker swarm:

https://docs.appdynamics.com/display/PRO45/Monitoring+Containers+with+Docker+Visibility

https://docs.appdynamics.com/display/PRO45/Configure+the+Standalone+Machine+Agent

https://docs.appdynamics.com/display/PRO45/Deploy+Using+Containers

Have used below parameters :

  • -Dappdynamics.docker.enabled=true
  • -Dappdynamics.docker.container.collection.cgroup.enabled=true
  • -Dsim.docker.monitorAPMContainersOnly=false
  • -Dappdynamics.agent.reuse.nodeName.prefix=<nodename>

  • -Dappdynamics.agent.reuse.nodeName=true

  • -Dappdynamics.jvm.shutdown.mark.node.as.historical=true

View solution in original post

Ravi_Verma
Engager

I have found out that we need to install app-agents inside the containers.

It can not work only with machine-agent installation/configuration, you need to use app-agents as well.

I have referred below articles which has helped me to run appdynamics for my docker swarm:

https://docs.appdynamics.com/display/PRO45/Monitoring+Containers+with+Docker+Visibility

https://docs.appdynamics.com/display/PRO45/Configure+the+Standalone+Machine+Agent

https://docs.appdynamics.com/display/PRO45/Deploy+Using+Containers

Have used below parameters :

  • -Dappdynamics.docker.enabled=true
  • -Dappdynamics.docker.container.collection.cgroup.enabled=true
  • -Dsim.docker.monitorAPMContainersOnly=false
  • -Dappdynamics.agent.reuse.nodeName.prefix=<nodename>

  • -Dappdynamics.agent.reuse.nodeName=true

  • -Dappdynamics.jvm.shutdown.mark.node.as.historical=true

Get Updates on the Splunk Community!

Uncovering Multi-Account Fraud with Splunk Banking Analytics

Last month, I met with a Senior Fraud Analyst at a nationally recognized bank to discuss their recent success ...

Secure Your Future: A Deep Dive into the Compliance and Security Enhancements for the ...

What has been announced?  In the blog, “Preparing your Splunk Environment for OpensSSL3,”we announced the ...

New This Month in Splunk Observability Cloud - Synthetic Monitoring updates, UI ...

This month, we’re delivering several platform, infrastructure, application and digital experience monitoring ...