Splunk AppDynamics

ERROR NetVizAgentRequest - Fatal transport error while connecting to URL

Loong_Ang
New Member

ERROR NetVizAgentRequest - Fatal transport error while connecting to URL [http://127.0.0.1:xxxx/api/agentinfo?timestamp=0&agentType=APP_AGENT&agentVersion=4.5.19]: org.apache.http.conn.ConnectTimeoutException: Connect to 127.0.0.1:xxxx [/127.0.0.1] failed: connect timed out

Been facing this error in agent log. Browser RUM data ok via injection into header of html files. Application monitoring shows connected, but no data received.

Using java agent and maven.

Labels (1)
0 Karma

Philip_Rogers
Path Finder

Hi Loong.Ang-

If you are not running the Network Visibility Agent, can you please disable socket instrumentation (netviz) using the below node property and then restart the application agent:

Name: socket-enabled
Description: socket-enabled
Type: Boolean
Value: false

 Note that you may need to manually create this node property if it does not exist. Information on how to edit a node property can be found in the following link:

https://docs.appdynamics.com/display/PRO45/App+Agent+Node+Properties

This error should not impact your application monitoring. If you edit this node property and are still having issues with the application monitoring not receiving data, it may be best to escalate directly to AppDynamics support:

https://help.appdynamics.com/hc/en-us/requests/

Get Updates on the Splunk Community!

.conf25 technical session recap of Observability for Gen AI: Monitoring LLM ...

If you’re unfamiliar, .conf is Splunk’s premier event where the Splunk community, customers, partners, and ...

A Season of Skills: New Splunk Courses to Light Up Your Learning Journey

There’s something special about this time of year—maybe it’s the glow of the holidays, maybe it’s the ...

Announcing the Migration of the Splunk Add-on for Microsoft Azure Inputs to ...

Announcing the Migration of the Splunk Add-on for Microsoft Azure Inputs to Officially Supported Splunk ...