AppDynamics Application Intelligence Platform
For optimal performance, there are default limits of 50 business transactions per app agent and 200 business transactions per business application. There is no limit at the tier level.
The app agent limit applies to each app agent, not to the machine. If you have multiple app agents on a single machine, the machine can handle the number of agents times 50.
If traffic exceeds the default limits, the traffic from what would be 51st detected business transaction and greater for the agent or the 201st and greater detected business transaction for the application is collected into a default business transaction called "All Other Traffic - <tier_name>". There is one of these "All Other Traffic" default transactions for each tier.
Some applications, such as those that create business transactions dynamically, can exceed the default limits very quickly. Since you want to monitor the business transactions that are key to your business, look at All Other Traffic and decide whether any of it needs to be reconfigured. See Managing All Other Traffic and Configure Business Transaction Detection.
The All Other Traffic business transaction displays according to its tier name in the Business Transactions List.
You can look at the instances of a default business transaction in the Business Transaction Dashboard.
The name used for All Other Traffic in the REST API is "APPDYNAMICS_DEFAULT_TX". See an example at Use the AppDynamics REST API
In most cases you want to examine the transactions in All Other Traffic and determine whether they represent important business transactions that you want to monitor or not. For example, if an All Other Traffic transaction is called frequently, you can define a custom rule for a new business transaction for that traffic. You can "trade off" and keep within the limits by excluding other business transactions, such as those that have little or no load, by using a custom exclude rule.
The following sections explain why there is a default limit on number of business transactions for app agents and the Controller.
After every minute, the Controller aggregates and monitors service levels of each business transaction and accepts data from multiple agents processing the same business transaction. The Controller stores data about those agents which identify the business transaction or the entry points and the data about other nodes (where the business transaction context is maintained).
The Controller I/O processing ability is affected by both the number of business transactions and the number of nodes in the application.
To learn more about what type of hardware can efficiently manage how many nodes and business transactions see Controller System Requirements.
The business transaction default limit for agents is very important because AppDynamics is designed for production environments. AppDynamics agents do not simply collect data and report it to the Controller, they also:
Imposing default limits on the number of business transactions is one way to manage the memory requirements of the agent in any type of application environment.
Before changing the limits, take into account the following factors:
To change the limits, contact AppDynamics Support.