Join the Conversation
- Find Answers
- :
- Splunk Platform
- :
- Splunk AppDynamics
- :
- EKS Agent: Failed to send agent registration reque...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark Topic
- Subscribe to Topic
- Mute Topic
- Printer Friendly Page
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm attempting to get an AWS EKS cluster instrumented with an AppD agent running against a SaaS instance.
I have followed the instructions here: https://docs.appdynamics.com/appd/4.5.x/en/infrastructure-visibility/monitoring-kubernetes-with-the-... as well as other guides.
The containers are running, but I get this error in the cluster agent logs:
[ERROR]: 2022-08-17 01:06:57 - agentregistrationmodule.go:131 - Failed to send agent registration request: Status: 404 Not Found, Body: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><title>Error report</title><style type="text/css"><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 404 - Not Found</h1><hr/><p><b>type</b> Status report</p><p><b>message</b>Not Found</p><p><b>description</b>The requested resource is not available.</p><hr/></body></html>
I have available Server Visibility licenses so that isn't the issue.
What can I do to get this working?
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I ended up having to work with AppD support on this one.
After some troubleshooting, we found that the controller URL in my cluster-agent.yaml file was incorrect.
I had a trailing slash and needed to specify the port, which in my case was 443. After fixing the yaml I had to apply the new file and then delete the old pod to get it to accept the new configuration.
It ended up looking like this:
controllerUrl: "https://<account_name>.saas.appdynamics.com:443"
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
iamryan
Hi @Josh.Ellsworth,
Thanks for sharing that!
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I ended up having to work with AppD support on this one.
After some troubleshooting, we found that the controller URL in my cluster-agent.yaml file was incorrect.
I had a trailing slash and needed to specify the port, which in my case was 443. After fixing the yaml I had to apply the new file and then delete the old pod to get it to accept the new configuration.
It ended up looking like this:
controllerUrl: "https://<account_name>.saas.appdynamics.com:443"
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
iamryan
Hi @Josh.Ellsworth - I was doing more research and saw you created a ticket. Can you share the results you get from that interaction here as a reply? Knowledging share is key for the community
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
iamryan
Hi @Josh.Ellsworth,
I found this existing Community post where the poster has a very similar error message. Can you check out the reply and see if it helps.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hey Ryan - thanks for reaching out. I have checked the linked articles before, but I still get the same results.
Splunk Search APIを使えば調査過程が残せます
Integrating Splunk Search API and Quarto to Create Reproducible Investigation ...
Congratulations to the 2025-2026 SplunkTrust!
