How Transactions are Gathered into All Other Traffic
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.
Viewing All Other Traffic
The All Other Traffic business transaction displays according to its tier name in the Business Transactions List.
To look at the All Other Traffic transactions
You can look at the instances of a default business transaction in the Business Transaction Dashboard.
- Select the business transaction from the list and click View Dashboard. Update the time range as needed.
- In the All Other Traffic dashboard click View Traffic Details.
The Traffic Details window displays a list of the auto-detected transactions that occurred after the limits were exceeded.
The Business Transaction Name column contains auto-generated names for the transactions. The Call column shows the number of instances of the transaction and the Type column shows the entry point type.
- If the Fetch more link is displayed, click it to see more calls. It retrieves 600 calls per click. If the Fetch more link is not displayed, there are no more calls to retrieve for the selected time range.
To get metrics for All Other Traffic using REST
The name used for All Other Traffic in the REST API is "APPDYNAMICS_DEFAULT_TX". See an example at Use the AppDynamics REST API
Managing All Other Traffic
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.
Business Transaction Limits for 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.
Business Transaction Default Limits for Agents
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:
- Observe service levels for each business transaction.
- Observe metrics, such as the number of slow requests, and start diagnostic data collection when thresholds are reached.
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.
Changing Business Transaction Default Limits
Before changing the limits, take into account the following factors:
- Controller hardware. For details see Controller System Requirements.
- Memory available for the agent on the managed JVM or CLR. To analyze the memory allowed for the agent:
- After the agent discovers 50 transactions, compare the current memory footprint of the JVM or CLR with that of the agent.
- Then, compare this data with the memory available for the agent.
To change the limits, contact AppDynamics Support.