Showing results for 
Show  only  | Search instead for 
Did you mean: 
AppDynamics Team

What are the steps when you want to increase Controller and Agent ADD limits?

This article includes instructions to remediate ADD limits at Controller and Account levels.



AppDynamics collects Application Diagnostic Data (ADD) with limits in place to prevent overhead. If any ADD limit is hit, either on the agent or on the Controller, a notification will appear and that particular type of ADD will not be registered. Therefore, it will not be tracked and report metrics, which can impact application visibility. It’s important that you not ignore these notifications.


For larger deployments with hundreds or thousands of agents and varied types of applications, the default limits are often minuscule. You can adjust the limits by following the remediation steps below.


Keep in mind that defining a high value for a property might add overhead, so be cautious.

For a fuller explanation of Controller and Agent ADD limits, see Controller and Agent ADD Limit Notifications: Explanations.


Table of Contents


Account-level limits after version 4.4

Prior to version 4.4 version, all ADD limits were stored only at the Controller level. Starting from version 4.4, we introduced limits at the Account level. This means that you can configure ADD limits at both Account and Controller levels. 


ADD limits stored at the Account-level can be further placed into:

  • Default Limits (for all Accounts) 

  • By Accounts (for individual Account in the Controller)


Limit Notification Example

Here is an example of a limit notification.



For a comprehensive list and explanation of limit notifications, see Controller and Agent ADD Limit Notifications: Explanations.

However, before tackling this, please look at the notification very carefully. specifically, at the Scope field: 


Scope: ACCOUNT means that the limit is hit at Account-level. Going back to the screenshot, the notification implies that the for Account id: 2, THREAD_TASK (ADD type) limit of 1000 has been reached.


Similarly, you will see a different value for a Scope field like Scope: CONTROLLER for limits hit at Controller-level


Pre-Requisites: Enabling Settings

Before increasing ADD limits, you must:


  1. Enable the Account-level limits page
  2. Enable the Controller Settings page


Enable Account-level limits page

Before changing the Account-level limits, the first step is to configure admin.jsp to show Account-level Limits. If the Account Limits tab is already enabled, skip this step and jump to the How do I change ADD limits? section below. If not, your view would be similar to this:  Screen Shot 2019-10-24 at 9.56.58 AM.png


To see the Account Limits tab:


  1. Go to Controller Settings
  2. Search for “platform” and view the Controller Configurations tab, listing appdynamics.platform.limits.account.enabled  



  3. Change the value of the property to true and click the Save button.
  4. Refresh the browser. After refreshing, the Accounts Limits page under admin.jsp should look something like this:

Screen Shot 2019-10-24 at 9.59.45 AM.png


Enable Controller-level limits page

Before changing the Controller-level limits, the first step is to configure admin.jsp to show Controller-level Limits. 


If the Controller Limits tab is already enabled, skip this step and jump to the How do I change ADD limits? section, below. If the Controller Limits tab is not enabled, your view would be similar to this:  image9.png



By default, the Controller Settings would look like this, with the Controller Limits tab not displayed. 



To view the Controller Limits tab and its contents: 

  1. Go to Controller Settings
  2. Search for “platform” and view the Controller Configurations tab, listing appdynamics.platform.limits.controller.enabled

  3. Change the value of the property to true and click the Save button on each of the two settings. 

  4. Refresh the browser. The updated page should display the Controller Limits tab.image7.png


How do I change ADD limits?

Once both the Account-level limits and Controller Settings page views are enabled and visible, you can update the ADD limit values. 


You will need to:


Update Account-level ADD Limits

  1. In Account Settings, under the Account Limits tab, check the Default Limits page for the value associated with the desired ADD type. If the Hard Limit value is 1000 (the default value for error ADD, as seen in the screenshot below), update it to a larger value.

  2. Go to the By Account tab and also update the Hard Limit value for the same ADD type with the same value you entered in the Default Limits tab in order to maintain consistency across the system.


Update Controller-level ADD Limits

  1. Under Controller Settings, search for desired ADD type in the Controller Configurations tab
  2. Update the Value field of the desired ADD to a higher value and click Save.


  3. Repeat the steps 1 and 2 for error ADD in Controller Limits.


NOTE: Be sure the value you enter at Account-level (in both the Default Limits and By Account pages) is not greater than the value in the Controller configurations. Because of our hierarchical model (where a Controller has many accounts), all the consolidated account-level limits should not be greater than the overall Controller-level setting.


If both controller.enabled and account.enabled are false does the ADD changes set work from the admin page?


Solved it by trial and error. Had to enable both and start to provision downwards from controller settings. A bit tedious for an on-prem installation with only one account. But the usage graphs were worth it for sure.


Thanks for this!

Version history
Last update:
‎10-30-2019 06:29 PM
Updated by:
June 26 Webinar
Discover new Splunk integrations and AI innovations for Cisco AppDynamics.

Register Now!

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

Read the blog here