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
01-30-2019 06:14 PM
Good Day!
Recently, we have frequent errors regarding "Agent Metric Registration Limit Reached". I searched the kbs and Google for possible answers and came up with this. We are trying to get much information regarding this error so that we can better plan on our next steps. With this, we have few questions and I hope you could help us with these:
I hope you could help us with these. Thank you very much!
06-12-2019 04:16 AM
Hi James,
Did you find the answers for your Questions ? Even i am encountering the Metric Registration limit Reached but not able to Identify Which metrics are the Culprit ? I Searched from Metric Browser, But didn't helped any ?
01-09-2020 07:56 PM
I think the only way may be to recursively call the API to retrieve the hierarchy as defined here: https://docs.appdynamics.com/display/PRO45/Metric+and+Snapshot+API
Mark
09-03-2021 05:43 AM - last edited on 09-03-2021 10:52 AM by Ryan.Paredez
Metric Registration increase as there is an increase in Auto Detected BTs or Auto detected Backend.
So try to see, whether the BT Count count exceeded 200 or not.
If Yes, then 1st try to work on reducing No. of Auto Discovered BTs,
for which you can change the configuration in "Automatic Transaction Discovery Rule"
e.g. Reducing segments of the URL for Servlet BT
or Disabling unwanted types of BTs and /or Backends
I hope this will help.
- Manish Upadhye
09-03-2021 10:54 AM
Hi @Manish .Upadhye,
Thank you for sharing that helpful info. @Bryan James.Ilaga, I know you asked this question a while ago. If this topic is still of any interest to you, please check out the reply from Manish.
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.
09-17-2021 12:15 AM - last edited on 09-17-2021 10:37 AM by Ryan.Paredez
We are seeing agent metric registration limit issue only on two servers where it only discovers 10 transactions. Rather than on other nodes, it discovers more than 100 transactions.
Will transactions generated from other servers also have an impact.
Other nodes are not giving any such warning
10-18-2021 03:51 AM
Hi Sumit,
Yes, transactions auto-generated / detected from other nodes / servers /Tiers also contribute to total BT count. As There is default limit of 200 BTs, on BT detection across particular Application.
So try to see, whether the existing BT Count exceeded 200 or not (across Application).
- Manish Upadhye
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