Splunk AppDynamics

Metric registration limit of 7500 reached

Sumit_Thakur
Engager

On a few Java servers.nodes in my environment /SaaS
was getting Warning Metric registration limit of 5000 reached. 

We have already increase the limit to 7500 on both nodes by adding parameters in the JVM startup file

-Dappdynamics.agent.maxMetrics=7500

  But again we are getting alert  "Metric registration limit of 7500 reached"

Appd is only discovering 10 Business transactions on these nodes but not sure why the limit is being reached again and again. Even other nodes are running 40 BT but there is no such alert. How can we fix it permanently and find out the root cause?  

Also on both of these servers HTTP Error is not being captured inside metric

Errors|EIS-Dxp|HTTP Error Code : 504|Number of Error

and

Errors|EIS-Dxp|HTTP Error Code : 502Number of Error

Is this issue also because of the metric registration limit? 

Labels (3)
0 Karma

iamryan
Community Manager
Community Manager

Hi @Sumit.Thakur,

Please see this existing post and let me know if it helped you out or not.

https://community.appdynamics.com/t5/Controller-SaaS-On-Premises/Agent-Metric-Registration-Limit-Rea...

0 Karma
Get Updates on the Splunk Community!

Accelerating Observability as Code with the Splunk AI Assistant

We’ve seen in previous posts what Observability as Code (OaC) is and how it’s now essential for managing ...

Integrating Splunk Search API and Quarto to Create Reproducible Investigation ...

 Splunk is More Than Just the Web Console For Digital Forensics and Incident Response (DFIR) practitioners, ...

Congratulations to the 2025-2026 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...