Transaction aggregation

This is used if you want to merge similar transactions into one.

For example, if transactions are identified by URL (name of the transaction = URL path) and you see the following URLs in the application: “/products/1234”, “/products/3210”, “/products/9876”, it is better to merge these transactions into one.

You can do this by selecting an application in the tab control and by adding appropriate aggregation rule. Rules can be edited after clicking Edit aggregations. Use the Create aggregation button to insert a new empty rule.

Using this button aggregation rules can be sorted. If the transaction complies with more aggregation rules, then the topmost rule in the table will be used.

There are two types of operations in the table:

Simple expression:

If the beginning of the transaction name starts with text in the rule, then the transaction is renamed to the value described by the rule. Wildcard * can be used 1x in the rule. See the following examples.

Examples:

Transaction	Rule	Result
/products/1234 /products/4567 /products/4567	/products	/products
/section1/people-2254 /section1/people-5841 /section2/people-4456 /section3/people-9853	/section*/people	/section1/people /section2/people /section3/people
/pre/products/123	/products	/pre/products/123 (rule does not match the beginning of the transaction, so the original transaction name will be used)

Regular expression

Extraction regular expressions can be applied to the transaction name. The resulting value in the regular expression must be enclosed in the parenthesis. If there is no match with the regular expression, the original transaction name is used. See the following examples.

Examples:

Transaction	Rule	Result
/products/1234 /products/4567 /products/4567	(/products)/[0-9]*	/products
/section1/people-2254 /section1/people-5841 /section2/people-4456 /section3/people-9853	(/section)[0-9]* (/people)-[0-9]*	/section/people
/pre/products/123	/products	/products
/aaa/bbb	(/ccc)	/aaa/bbb
/section1/people2/name3 /section1/people2/name4 /section1/people2/name5 /section4/a1/b2/c3/d4/e5	^(/[^/]* /[^/]* /).*$	/section1/people2 /section1/people2 /section2/people2 /section4/a1

Aggregation is applied to the newly processed transaction; the old transactions remain without change.

For an aggregation of the old transactions, click Start backward aggregations:

• Select aggregations – selection of the aggregate rules.

• Delayed start – late start at a specified time.

• Start at – the backward aggregation will be scheduled at the specified time if a Delayed start is active.

• Start – start or schedule the backward aggregation. Processes can run from seconds to several hours, depending on the number of transactions. Backward aggregations for large databases are recommended over the weekend.

• Stop – cancel running the backward aggregation.

Recommended aggregations

For ease of setting aggregation rules, you can use the Recommended aggregation. Set the Aggregation count to reduce the maximum count of recommended aggregations. The recommended aggregation rule will aggregate at least the Min. transaction count number of transactions. To view the recommended aggregation click Search.