UMA Java agent auto-attach fails due to existing Introscope properties

Products

• DX SaaS
• DX Operational Observability
• DX Application Performance Management

Issue/Introduction

The Universal Monitoring Agent (UMA) Java agent fails to attach to application containers via the auto-attach mechanism. The sidecar container starts and finishes, but the main application container remains unmonitored.

Symptoms

The following log entry appears in the podmonitor or apm-probe-autoattach logs:

Process in container is being skipped since the application contains introscope properties and possibly being already monitored by wily agent. Please remove all introscope properties including -javaagent before proceeding.

Additionally, the annotations ca.broadcom.com/probe-autoattach.type and ca.broadcom.com/probe-autoattach.status are missing from the pod definition.

Environment

• DX SaaS (DX APM)
• Universal Monitoring Agent (UMA)
• OpenShift / Kubernetes
• Java applications (Tomcat, etc.)

Cause

The UMA auto-attach mechanism (Attacher) identifies the Java process but aborts the instrumentation because it detects existing legacy Introscope properties or a manual -javaagent flag within the application's environment variables or startup command. UMA skips instrumentation to prevent conflicts with an existing agent.

Resolution

To allow UMA to successfully auto-attach the Java agent, you must remove all manual agent configurations from the deployment specification:

1. Review the Deployment or DeploymentConfig for the target application.
2. Identify and remove any JAVA_TOOL_OPTIONS or startup arguments containing -javaagent:####/Agent.jar.
3. Remove any environment variables prefixed with introscope.* (e.g., introscope.agent.name).
4. Redeploy the application. UMA will now detect the clean process and inject the sidecar agent automatically.

If you require further assistance, see Contact Broadcom Support.

Additional Information

• UMA Application Monitoring Documentation
• Universal Monitoring Agent Troubleshooting