Splitting options

Use the Splitting Options dialog box to define how to limit the number of splitting values for a Business Transaction. Setting a maximum number of splittings helps to keep the results comprehensible and protect your AppMon environment from overload. To access the dialog box, in the the Business Transaction Editor dialog box, click Splitting Options.

You can also reset the current set of splitting values for any application configured in your System Profile.

Splitting options dialog box
Splitting options dialog box

Restrictions

When you configure a splitting restriction, the splitting values of an application are determined based on an initial set of transactions. This set is one of the following, depending on the load:

  • All transactions in an observation period of one minute.
  • The first 500 transactions that are collected, if fewer than 500 transactions occur within one minute.

With a sufficient load, there can be more than 500 transactions in the set. The final splitting values are calculated by taking the contribution of every splitting value of a transaction into account. Splitting values with a small contribution are mapped to a remainder splitting value.

Limit to most frequent transactions

From the initial set of transactions, only the X most frequently observed splitting values establish a splitting. Other splitting values are mapped to the remainder splitting value <...>. The upper limit, X, can be five through 100.

Limit to minimum contribution

From the initial set of transactions, the observed splitting values with a contribution of X or larger establish a splitting. Other splitting values are mapped to the remainder splitting value <...>. The minimum contribution, X, can be 1% through 50%.

Aggregate to common URI patterns

The observed splitting values in the initial set of transactions are assumed to contain URIs. The segments are delimited by the slash (/) character. The minimum contribution of a segment can be 1% through 10%. Segment contributions that are less than the defined minimum are mapped to the <...> segment.

For example, the initial set of transactions contains 500 items. For this Business Transaction, the minimum segment contribution is 1%. So at least five transactions of the same segment must occur to get a distinct splitting.

The table illustrates the results of five transactions: four involving images/**ex1**/ and one involving images/**ex2**/.

URI Resulting Splitting Values Reason
images/**ex1**/ (none)  
images/**ex1**/ (none)  
images/**ex1**/ (none)  
images/**ex1**/ (none) Segment ex1 occurs only four times and therefore does not reach the minimum contribution.
images/**ex2**/ images/<...>/ Segment images occurs five times and therefore reaches the minimum contribution.

Note

The splitting measure source can be a method argument or return value. This restriction can be applied to any input separated by slashes (/).

Restrict to

This setting specifies the maximum number of splittings for the Business Transaction. The value can be 100 through 50,000.

No restriction

When No restriction is selected, there is no observation period for limiting splitting values. Every distinct splitting value in a Business Transaction establishes a new splitting value or measure.

Note

If you select No restrictions for a URI splitting measure and your application uses a sessionID parameter, the number of splitting values can increase rapidly and fill up the Performance Warehouse. See Preventing Excessive Split Results for more information.

Business Transactions created in AppMon 4.2 or earlier have the default setting of No restrictions. They are not automatically migrated to restrict splitting results.

For a new Business Transaction, the default is to split by the 30 most frequent transactions. When adding the splitting measures Complete URI Path, the restriction is set to Aggregate to common URI patterns with a minimum contribution of 5%.

Reset splittings

If a splitting restriction is active for a Business Transaction, you can reset the calculated splitting values separately for every configured application. After a reset, the splitting values determination process — the initial observation period — is started automatically for the application.

A reset can be helpful if an atypical set of transactions was recorded during the observation period. For example, the observation period included maintenance transactions, but you want to observe only user-generated transactions.

To perform a reset, select the required application from the list, and click Reset.