Splunk AppDynamics

EKS Agent: Failed to send agent registration request: Status: 404 Not Found

Josh_Ellsworth
Explorer

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? 

Labels (1)
Tags (2)
0 Karma
1 Solution

Josh_Ellsworth
Explorer

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"

 

View solution in original post

iamryan
Community Manager
Community Manager

Hi @Josh.Ellsworth,

Thanks for sharing that! 

0 Karma

Josh_Ellsworth
Explorer

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"

 

iamryan
Community Manager
Community Manager

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 

0 Karma

iamryan
Community Manager
Community Manager

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.

https://community.appdynamics.com/t5/Infrastructure-Server-Network/Kubernetes-cluster-agent-can-not-...

Josh_Ellsworth
Explorer

Hey Ryan - thanks for reaching out. I have checked the linked articles before, but I still get the same results.

0 Karma
Get Updates on the Splunk Community!

Splunk Observability Cloud's AI Assistant in Action Series: Auditing Compliance and ...

This is the third post in the Splunk Observability Cloud’s AI Assistant in Action series that digs into how to ...

Splunk Community Badges!

  Hey everyone! Ready to earn some serious bragging rights in the community? Along with our existing badges ...

What You Read The Most: Splunk Lantern’s Most Popular Articles!

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...