The Performance Analyst should first investigate the Business Transactions exceeding the configured limit and determine why so many unique transactions are being registered. Business Transaction limits protect the Controller from excessive metric creation, unnecessary cardinality, and degraded monitoring performance.
A high transaction count is often caused by overly granular transaction naming, dynamic URL segments, request parameters, identifiers, or automatic discovery rules that create a separate Business Transaction for each variation. The analyst should review All Other Traffic, transaction detection rules, naming rules, and the entry points generating excessive registrations. Low-value traffic such as health checks, static resources, or framework-generated requests can be excluded, while related requests can be grouped or split more deliberately through Custom Match Rules.
Increasing the limit without correcting the underlying detection behavior may only postpone the problem and increase Controller resource consumption. The limit should be raised only after the transaction model has been validated and a genuine business requirement remains.
Relevant CAAPA Study Guide topics include Business Transaction Limits, All Other Traffic, Transaction Detection Rules, Custom Match Rules, Exclude Rules, Transaction Naming, and Metric Cardinality Management.
