A Performance Analyst is reviewing Business Transactions with an Application team. The Application team would like to increase the Application…

AppDynamics enforces Business Transaction (BT) limits (typically 50 per node, 200 per application) to prevent "BT explosion," which can degrade Controller performance and clutter the UI. When an application team requests a limit increase to see "all" transactions, it usually indicates poorly configured BT discovery rules, such as unparameterized URLs or dynamic data in transaction names. Instead of blindly increasing the limit, a Performance Analyst should investigate why the limit is being exceeded. By focusing on the overflow traffic (often grouped in "All Other Traffic"), the analyst can create custom match, exclude, or grouping rules to capture the truly critical business functions without overwhelming the system.

A: The limit is highly important; ignoring it leads to BT explosion and severe performance degradation on the Controller.

B: Blindly increasing the limit degrades Controller and Agent performance and violates AppDynamics best practices for BT management.

C: Arbitrarily increasing the limit halfway does not solve the root cause of the BT explosion and still risks performance issues.

Cisco AppDynamics Official Documentation: "Business Transaction Limits" (Section: Business Transaction Management).

Cisco AppDynamics Official Documentation: "Organize Business Transactions" (Section: Resolving BT Explosion).