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.
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)
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
Before increasing ADD limits, you must:
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:
To see the Account Limits tab:
admin.jspshould look something like this:
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:
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:
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:
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.