cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Sayantan.Mitra
AppDynamics Team

Troubleshooting Agent Registration Failures Due to Unauthorized Errors in Observability Systems

There can be a multitude of reasons why an agent is unable to register with the controller but if the agent logs an HTTP 401 or Unauthorized error in the logs then it can be safely ruled out that the network is the issue as this is usually returned from the controller when the request sent does not fit the allowed criteria for the controller.

Unauthorized errors happen when an agent tries to register with improper credentials or the controller has a scope on the rule due to which the agent registration is denied.

The 4 distinct params which help the agent to connect to the controller are:

  • Controller host name
  • Controller port
  • Access key
  • Account name.

If the controller is TLS enabled then the flag ssl-enabled is crucial and so does the port change. 

Each agent takes these params differently, so please refer to the documentation on how to configure the agent. 

However, some agents require a different way

Cluster agent - first create the secret in the appdynamics namespace 

kubectl -n appdynamics create secret generic cluster-agent-secret --from-literal=controller-key='<access-key>' --from-literal=api-user=‘<username@account:password>’

If the above is not done then the CA yaml must have these details populated.

If the configuration on the agent side is not the issue then this can be an issue on the controller license i.e. the accesskey you have used. Please ensure that the access key has valid units of a license, as well as there, is no Application or Server scope that is blocking the registration from happening between the agent and controller.

A quick way to test is to create a new license from the default and ensure just 1 unit of license is given to that rule. Then use this as the accesskey and try registering the agent. If it succeeds the license rule used before was the culprit.

If these still don't help please raise a case with support and provide screenshots of the agent configuration, the logs from the agent end, and a screenshot of the license rule which shows the available units and scopes.

Version history
Last update:
‎09-10-2024 10:40 AM
Updated by:
On-Demand Webinar
Discover new Splunk integrations and AI innovations for Cisco AppDynamics.


Register Now!

Observe and Explore
Dive into our Community Blog for the Latest Insights and Updates!


Read the blog here