By default, AppDynamics allows a maximum of 200 registered Business Transactions per application and 50 Business Transactions per node.
The application-level limit controls the total number of unique Business Transactions that can be registered across all tiers and nodes belonging to the application. The node-level limit restricts how many transactions a single Application Agent can independently discover and register. These safeguards prevent uncontrolled Business Transaction growth, excessive metric creation, and unnecessary Controller resource consumption.
When either limit is reached, newly discovered requests are not registered as individual Business Transactions. Instead, they are typically grouped into an All Other Traffic category for the affected tier or entry-point type. Important transactions can still be prioritized by creating Custom Match Rules, excluding low-value traffic, refining transaction naming, or adjusting registration limits where operationally justified.
The application limit is not 100 or 300 by default, and the node limit is not 75 or 200.
Relevant CAAPA Study Guide topics include Business Transaction Registration Limits, Application and Node Limits, All Other Traffic, Automatic Transaction Discovery, Custom Match Rules, Exclude Rules, and Business Transaction Lock Down.
