Hi Abhilash,
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.
Follow the steps below to resolve this error message:
1. First control the metric registration limit from the agent side after deleting the unwanted business transactions, information points, service endpoints and back ends. You can then try resetting 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.
-Dappdynamics.agent.maxMetrics=<IntegerNumber>
Also, You can group you BT/backend in one backend/BT so you can control the metric limit
https://docs.appdynamics.com/display/PRO45/Backend+Detection+Rules#BackendDetectionRules-all_other_t...
https://docs.appdynamics.com/display/PRO45/Business+Transactions#BusinessTransactions-RefineBusiness...
Note:
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 utilization 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 every-time you encounter this error is not the solution.
Suresh Rapaka
