cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
The AppDynamics Community is Migrating this Friday, February 28th.


At 6pm PST, the AppDynamics Community will go into read-only mode and after migration is complete, you will be redirected to community.splunk.com.
Read more here


Metric Registration blacklist limit reached - AGENT_METRIC_BLACKLIST_REG_LIMIT_REACHED

Anonymous
Not applicable

Hi 

Can someone explain how to fix below Event?

 

Severity
 Error
Type
AGENT_METRIC_BLACKLIST_REG_LIMIT_REACHED
Time
04/12/18 8:29:46 AM
Summary
Metric registration blacklist limit reached. Future metrics will not be registered.

Tier

Node

No Actions Executed
 
^ Post edited by @Ryan.Paredez to remove broken images.
 
2 REPLIES 2

Pratik.Maskey
AppDynamics Team (Retired)

Hi,

 

Please refer following KB article for more details.

 

 

https://community.appdynamics.com/t5/Knowledge-Base/How-to-resolve-an-error-when-reaching-the-agent-...

 

Thanks



Found something helpful? Click the Accept as Solution button to help others find answers faster.
Liked something? Click the Thumbs Up button.

Anonymous
Not applicable
This is what we did:
1. Issue: metric registration errors and blacklisted
2. We checked the metric limits.
3. We deleted some of the unused applications.
4. We were using Websphere MQ extension.We also added some of the queues to the exclude filters in WMQMonitor in order to reduce the metric footprint.
5. We restarted the MachineAgent and the metrics started reporting both WMQMonitor and ProcessMonitor metrics.
Ask the Experts Session: Hybrid Application Monitoring Deployment

Join us on Feb 26 to explore Splunk AppDynamics deployment strategies, SaaS models, agent rollout plans, and expert best practices.


Register Now

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


Read the blog here