AppDynamics Cluster Agent: Correlation with Crio container (OpenShift)

[#1]

Integrating AppDynamics Cluster Agent with Crio Containers in OpenShift Environments

We can enable correlation between cluster agent pods/containers and your APM node. 

• Add customAgentConfig to your cluster-agent.yaml file
  

  customAgentConfig: "-Dappdynamics.container.id.prefix=crio"​

• Remove instrumentation and do a redeployment for it to take effect
• The UNIQUE_HOST_ID of this application will become your container ID afterward
  
  The problem is that the 1.25 container runtime is Crio and by default, CA/JA looks for docker. If you check the UNIQUE_HOST_ID of your application right now, you will see the pod name as the UNIQUE_HOST_ID.
  
  
• Edit your cluster-agent.yaml file and add the above parameter
• Your yaml will look like the code example below

instrumentationRules:
 namespaceRegex: abhi-java-apps
 language: java
 appNameLabel: app
 customAgentConfig: "-Dappdynamics.container.id.prefix=crio"

• Once done remove the instrumentation from your application
• The quickest way would be to do kubectl delete and kubectl create again of your application
  • Or, you can set instrumentationMethod: None in cluster-agent.yaml and do a redeployment. 
• Once you see your application deployment without an APPD-related ENV variable add the parameter and do a kubectl apply -f / create -f
• Give it 10mins or so once your application starts reporting to the controller