Transaction Grouping in APM Insight allows you to aggregate multiple individual transactions under a single named logical entity called a Transaction Group. This helps simplify your monitoring view and makes it easier to analyze performance metrics across related transactions.
Instead of viewing hundreds of individual URL transactions like /api/users/123, /api/users/456, /api/users/789, you can group them under a single "User API" entry. Each group is treated as a Business Transaction in Applications Manager.

Most applications generate hundreds of individually tracked URL transactions. Without grouping, your transaction list becomes cluttered and difficult to analyze. Transaction Grouping solves this problem by allowing you to:
You can define transaction groups using either one of these methods:
| Method | Description | Use Case |
|---|---|---|
| Regex Pattern | Members are transactions whose name matches a regular expression pattern (for example, ^/api/users/\d+$) | Dynamic URLs with IDs where match is automatic and continuous |
| Manual Addition | Specific transaction IDs are explicitly added to the group | Curated sets of unrelated URLs that you want to monitor together |
When you create a Transaction Group, the following metrics are aggregated across all member transactions:
| Metric | Aggregation Method | Notes |
|---|---|---|
| Average / Min / Max Response Time | Sum then divide by count | Calculates weighted averages across all members |
| Throughput (RPM) | Sum across all members | Total requests per minute for the group |
| Apdex Score | Recomputed from aggregated data | Sum of satisfied, tolerating, and frustrated counts, then recalculated |
| Error Count / Error % | Aggregated per time window | Errors from all member transactions combined |
| Component Breakdown | Sum across all members | Time spent in each application component |
| Traces | Fetched on demand | Retrieved for member transactions when required |
Transaction Grouping is supported for the following transaction types:
To create a new Transaction Group:


Note: When using regex patterns, ensure your pattern is valid and matches the intended transactions. Test your regex with a few transactions before applying it to the group.
Once you have created Transaction Groups:


It allows us to track crucial metrics such as response times, resource utilization, error rates, and transaction performance. The real-time monitoring alerts promptly notify us of any issues or anomalies, enabling us to take immediate action.
Reviewer Role: Research and Development