Not a customer? Click the 'Start a free trial' link to begin a 30-day SaaS trial of our product and to join our community.
Existing Cisco AppDynamics customers should click the 'Sign In' button to authenticate to access the community
03-15-2024 08:30 AM - last edited on 03-15-2024 09:07 AM by Ryan.Paredez
Getting below mentioned error in logs of appdynamics cluster agent
[ERROR]: 2024-03-15 14:36:30 - agentregistrationmodule.go:132 - clusterId: -1
[ERROR]: 2024-03-15 14:36:30 - agentregistrationmodule.go:134 - Registration properties: {}
[INFO]: 2024-03-15 14:37:30 - agentregistrationmodule.go:119 - Initial Agent registration
[ERROR]: 2024-03-15 14:37:30 - agentregistrationmodule.go:131 - Failed to send agent registration request: Status: 401 Unauthorized, Body: <!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<title>Unauthorized</title>
</head>
<body>
HTTP Error 401 Unauthorized
<p/>
This request requires HTTP authentication
</body>
</html>
I'm very new to appdynamics and I had make its implementation asap
I'm running a k8s cluster in minikue right now and configured the cluster agent through Helm chart
I assume there is some issue with the values I have set in the values.yml file
03-18-2024 08:47 AM
Hi @Hassaan.Javaid,
Please check out this existing post and let me know if it helps: https://community.appdynamics.com/t5/Infrastructure-Server-Network/Kubernetes-cluster-agent-can-not-...
Thanks,
Ryan, Cisco AppDynamics Community Manager
Found something helpful? Click the Accept as Solution button to help others find answers faster.
Liked something? Click the Thumbs Up button.
Check out Observabiity in Action
new deep dive videos weekly in the Knowledge Base.
03-21-2024 09:29 AM
Hi @Hassaan.Javaid,
Did you get a chance to check out that linked post?
Thanks,
Ryan, Cisco AppDynamics Community Manager
Found something helpful? Click the Accept as Solution button to help others find answers faster.
Liked something? Click the Thumbs Up button.
Check out Observabiity in Action
new deep dive videos weekly in the Knowledge Base.
04-19-2024 12:37 AM
Hi Hassan,
This is a generic 401 authentication problem. When you send metrics or valid messages from agent to controller there are several things you have to configure properly below
host, port, account name (default "customer1" if you don't use the controller in a multi-tenant mode), and account key.
So basically there are 2 reasons that you need to focus.
First can you please control this step below given, and try again?
To create a secret with a Controller access key:
$ kubectl -n appdynamics create secret generic cluster-agent-secret --from-literal=controller-key=<access-key>
Thanks
Cansel
User | Count |
---|---|
2 | |
1 | |
1 | |
1 | |
1 | |
1 |
Thank you! Your submission has been received!
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form