What happens when the limit is reached?

No negative impact on existing monitoring. All already-tracked items continue to be fully monitored (call frequency, response times, metrics remain visible). Only new unique entries beyond the limit are dropped. Existing entries that become unused/inactive are automatically cleaned up after the Raw Data Retention period (default 10 days), freeing up room for new ones.

1. Limits apply at APM Insight Application level, NOT per Instance.
   
2. Configure from: Settings Tab > Performance Polling > APM Insight > Data Collection Limits.
   

Important: Only Web Transactions and Background Transactions can be grouped/optimized via agent config. All others (DB Operations, Exceptions, Components, App Parameters) cannot — only option is increasing the limit.

1. Agent config options to reduce count:
   
1. List of URL extensions to be skipped from tracking. 
   
2. List of exceptions to be skipped from tracking.
   
3. Skip Transactions.
2. Java Agent: Group Similar Transactions | Context based Monitoring
   
3. .NET Agent: Group Similar Transactions
   
4. Ruby Agent: Group Similar Transactions
   
5. PHP Agent: Group Similar Transactions
   

Note: Grouping affects only new transactions. Existing ones clean up after Raw Data Retention period (default 10 days) if unused/inactive. For quick cleanup, contact appmanager-support@manageengine.com with exported Transaction list:

1. APM tab > Your Application/Instance > Transaction tab > 'Fetch All Applications' (bottom) > 'Export as Excel' (right corner).
   

1. These cannot be grouped or optimized. Only option: increase limits within the allowed range: