UMA Java Agent autoinjection not working

Products

• DX SaaS
• DX Operational Observability

Issue/Introduction

You encounter an issue where the Universal Monitoring Agent (UMA) is unable to detect application pods and containers despite configuring the required annotations. 

Environment

• Product: DX SaaS (DX APM)
• Component: Universal Monitoring Agent (UMA)
• Environment: Kubernetes / OpenShift 

Cause

The issue occurs because the applications you are attempting to monitor are not Java-based or are not supported by the current UMA auto-attach capabilities. UMA requires specific prerequisites and supported technology stacks to successfully detect and attach to containers.

Resolution

To resolve this detection issue, you must verify that your application meets the UMA monitoring requirements:

1. Verify Technology Support: Confirm that your application uses a supported runtime, such as Java. UMA auto-attach does not currently support non-Java applications or specific unsupported frameworks.
2. Check Pod Logs: Review the probe-autoattach logs for entries indicating whether a pod was whitelisted or processed. Look for messages such as [INFO] [I.AutoAttach.Kubernetes.Overrider] Got new qualified pods list or [INFO] [I.A.Java.UnixContainerAttacher] Container #### is processed.
3. Validate Annotations: Ensure that the annotations configured on your deployment or pod match the expected UMA syntax.
4. Consult Documentation: Review the UMA Application Monitoring documentation for a complete list of supported technologies and prerequisites.

If your technology is not supported, this is considered a limitation of the current version. An enhancement request (DE674114) has been created to improve supportability metrics and centralize prerequisite documentation for UMA.