Node.js auto-attach fails or rolls back in UMA due to port 5005 restriction

Products

• DX SaaS
• DX Operational Observability

Issue/Introduction

Introduction Node.js applications fail to monitor or trigger an automatic deployment rollback after UMA auto-attachment is enabled. This occurs when the application pod cannot communicate with the Infrastructure Agent (UMA) running on the worker node.

Symptoms

• Auto-attachment mutation succeeds, but metrics do not appear in the DX APM console.
• Application pods roll back or restart repeatedly after the nodejs-probe-autoattach init container runs.
• Logs indicate connection errors to the worker node IP on port 5005.

Environment

• DX SaaS
• Universal Monitoring Agent (UMA)
• Node.js applications on Kubernetes or OpenShift

Cause

The Node.js agent communicates with a dxAPM component (Infrastructure Agent) running with hostNetwork. This requires traffic from the application pod to the worker node IP on port 5005 (default for ARF protocol). If a NetworkPolicy or external firewall restricts pod-to-node communication, the probe fails to connect.

Ports requirement

Specify the port number for the Infrastructure Agent.
Default Value: For ARF protocol, 5005

Resolution

1. Ensure port 5005 is open for communication from the application POD to the Worker Node IP.
2. If using the HTTP protocol instead of ARF, ensure port 8085 is open.
3. Add the following annotation to the application deployment to ensure the Node.js process is whitelisted: ca.broadcom.com/autoattach.nodejs.whitelistedProcess: '.*'
4. Ensure --no-node-snapshot is added to the NODE_OPTIONS environment variable if the application uses modern Node.js versions that conflict with the probe's snapshotting.
5. For HTTP protocol overrides, use: ca.broadcom.com/autoattach.nodejs.agent.overrides: 'APM_ENV_PROTOCOL=http,COLLECTOR_AGENT_PORT=8085'

Additional Information

• Refer to Node.js Agent Configuration for more details on port settings.