Java (Java Agent, Installation, JVM, and Controller Installation)

cancel
Showing results for 
Search instead for 
Did you mean: 

Anyway to get around the Backend Registration Limit of 300 for an Agent?

SOLVED
Highlighted
Builder

Anyway to get around the Backend Registration Limit of 300 for an Agent?

Is there anyway to get around the backend registration limit of 300 for an agent? I have a project that has around 600 web services it connects to, and they do not want to group them with discovery rules. Thanks!

Anyway to get around the Backend Registration Limit of 300 for an Agent?
1 REPLY 1
AppDynamics Team

Re: Anyway to get around the Backend Registration Limit of 300 for an Agent?

Hi Jonathan,

 

We have 300 backend limit from agent side. We have to increase the backend limit from agent side. 
We, however, suggest deleting the unwanted backend which is not reporting. Note that, increase the backend limit in agent cause overhead. But if you still want to increase the backend limit, please apply the node property in the controller UI. For applying the node property please follow the below docs.

https://docs.appdynamics.com/display/PRO43/App+Agent+Node+Properties

Property Name:- max-discovered-backends 
Property Type:- Integer
Property Value:-<no of backend to increase default is 300>

 

Thanks,

Atyuha



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