Application to Node Correlation with Kubernetes Alerting

When you enable the Kubernetes Alerting and new UI features, AppDynamics re-registers the containers. During this process, although application monitoring continues uninterrupted, the application to node correlation links for existing, successfully instrumented pods may not get displayed on the UI.

To restore these correlation links, you can use one of the following two approaches:

Scheduled Application Redeployment

The application to node correlation links are automatically restored when pods are restarted during your next scheduled application upgrade. Newly created containers will automatically establish and display the correlation links.

Forced Re-instrumentation

If you require immediate visibility of these links without waiting for a scheduled upgrade, you can use the enableForceReInstrumentation property. When this flag is enabled, the Cluster Agent performs a sequential restart of all pods for applications that were already successfully instrumented.

Note: The enableV2Metrics property must be set to true. Contact your AppDynamics customer support to enable this property.
To enable forced re-instrumentation, add the following property to the Cluster Agent configuration file:
CODE 
enableForceReInstrumentation: true
Note:

  • The Cluster Agent restarts pods in a sequential manner to minimize impact, but you should still monitor your environment during this process.

  • When all the relevant applications have been re-instrumented and the correlation links are available in the UI, it is recommended to set enableForceReInstrumentation back to false.