Knowledge Base

Showing results for 
Search instead for 
Did you mean: 

How do I resolve an error when reaching the agent metric registration limit?


When an agent tries to register more than 5000 metrics, it will fire the error below to the Controller. The default limit is 5,000 and once it has been met, the agent will not register new metrics. Mostly seen when users try to register Custom Metrics with incorrect configurations.





Follow the steps below to resolve this error message:


1. First control the metric registration limit from the agent side after deleting the unwanted businesss transactions, information points, service endpoints and backends. You can then try reseting the agent.


2. If all of the metrics are still required, you can increase the agent metric registration limit using the system property below and restarting the agent.




1. There is a reason why we have these limits.Be careful when increasing the metric registration limit. Before doing so, check your current CPU and memory utlization from the application side. A drastic increase of agent limit can affect the Controller.

2. Identify which metrics are registered, and focus only on relevant metrics. Increasing the limits everytime you encounter this error is not the solution. 

Version history
Revision #:
5 of 5
Last update:
‎10-04-2018 03:50 PM
Updated by:
Labels (1)

Found this article helpful? Click the Thumbs Up button.
Have an additional comment? Post it below.
0 Kudos

Regarding this matter, we have an extra large Appdynamics setup and we are finding many metric reg limit exceeded.

The question, reading your manuals is:

Which most common errors can be seen as incorrect, that produces exceeded limits?

Thanks for your kind answer.

@Fernando.Villava The limit you are seeing here is the agent side limit so the agent will send or register up to 5000 metrics to the controller and after that, if you are trying to register any BT, Backend, SEP agent will not register those metric to the controller UI.

and you will see the agent limit reached message on agent logs as well on controller UI.


Now there are so many reasons for reaching the limit

1) You are monitoring so many BT's and due to that agent is reaching the limit.

2) You are creating so many backends due to that you are reaching the limit.

3) You are registering too many mbean from the same node due to that you are reaching the limit.



How to resolve 

1) If you have sufficient heap space and your CPU utilization is normal you can increase the agent metric registration limit using below mentioned property




2) You can group you BT/backend in one backend/BT so you can control the metric limit