APM Correlation on OpenShift 4.x

Container Runtime Interface using OCI (Open Container Initiative) compatible runtimes (CRI-O), is the default container runtime on Red Hat Openshift 4.x. If you use APM Agents with OpenShift 4.x, you must update the UNIQUE_HOST_ID to support the syntax required for CRI-O containers. This setting applies to both new and existing application containers. If you are running App Agents, then you must modify the App Agent YAML file.

To run App Agents with APM correlation on Openshift 4.x:

  1. Open your App Agent YAML file.
  2. Locate the spec: > args: section within the file.
  3. Update the UNIQUE_HOST_ID argument in the containers spec using this example as a guide:.
    JSON 
    spec:
containers:
- name: client-api
command: ["/bin/sh"]
args: ["-c", "UNIQUE_HOST_ID=$(sed -rn '1s#.*/##; 1s/(.{12}).*/\\1/p' /proc/self/cgroup) && java -Dappdynamics.agent.uniqueHostId=$UNIQUE_HOST_ID $JAVA_OPTS -jar /java-services.jar"]
envFrom:
- configMapRef:
name: agent-config
    If APM Correlation is working correctly, when you click the Pod Details link, the link opens the APM Node Dashboard for that node