Splunk AppDynamics

The remote name could not be resolved

gurusiddappagou
New Member

Hi Team,

I have installed the .net agent on the windows server and it shows waiting for a connection. When I checked in AgentLog it shows the below error, please help how to fix this issue.

2022-03-15 09:55:34.1093 29580 AppDynamics.Coordinator 1 28 Warn MachineAgentManager Metrics Error sending metric data to controller:System.Net.WebException: The remote name could not be resolved: '[Redacted].saas.appdynamics.com'

   at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)

^ Post edited by @Ryan.Paredez to redact Controller name. Please do not share your Controller name or URL for security and privacy purposes. 

Labels (1)
Tags (2)
0 Karma

Hirokazu_Mori1
Path Finder
 
Thank you for posting a question on the community!
First of all, I recommend checking your network between a controller and the windows server.
By executing nslookup command on the windows server, you can make sure if the controller host name cam be resolved correctly.
nslookup <Your Controller Name>.saas.appdynamics.com
 
If it fails, there might be some problems on the network.
And if a proxy server exists between the controller and the windows server, you also need to configure proxy settings.
 
The document link to proxy configuration:
 
Please let us know if you have any questions.
 
 
Best regards,
 
Hirokazu
Get Updates on the Splunk Community!

New This Month - Splunk Observability updates and improvements for faster ...

What’s New? This month, we’re delivering several enhancements across Splunk Observability Cloud for faster and ...

What's New in Splunk Cloud Platform 9.3.2411?

Hey Splunky People! We are excited to share the latest updates in Splunk Cloud Platform 9.3.2411. This release ...

Buttercup Games: Further Dashboarding Techniques (Part 6)

This series of blogs assumes you have already completed the Splunk Enterprise Search Tutorial as it uses the ...