AppDynamics Application Intelligence Platform

3.8.x Documentation



Release Notes

Child pages
  • All Other Traffic Business Transaction

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: move bt limit discussion to here 26758


To learn more about tuning business transactions see Organizing Traffic as Business Transactions and Configure Business Transaction Detection.

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:

  • 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.

Learn More