Business Transaction configuration

You can create business transactions through the System Profile, or at the Business Transactions page of the Monitoring dashboard. This page describes editing in the System profile. To read about the Business Transactions page, refer to Business Transaction page of the Monitoring dashboard.

To configure a Business Transaction:

  1. Open the System Profile Preferences dialog box, and select the Business Transactions item.
  2. Click Create to create a new Business Transaction, or select a Business Transaction from the list and click Edit.
  3. Enter information and select settings as needed, then click OK to save the settings. See below for parameters description.

AppMon 2018 April and later You can also hold Shift and click the required BT in the Business Transactions sub-bar.
AppMon 2017 May You can also right-click the required BT in the Cockpit and select Edit Business Transaction from the context menu.


This section contains general settings of the business transaction:

  • Name: The name of the business transaction. The name must be unique within a System Profile and cannot be empty.
  • Description: Short description of the business transaction.
  • Store results in Performance Warehouse: Enables storage of the captured transactions in the Performance Warehouse.
  • Export results via HTTP: Enables real time Business Transaction feed to external systems for further storage and analysis. When activated, you can include the following additional data to the stream:
    • PurePaths reference
    • Performance data

Calculate Business Transaction performance

Select the entity for business transaction capturing.


Use filters to restrict the PurePaths, user actions, and visits for which the Business Transaction should be evaluated. For example, you can add a specific filter that checks for the occurrence of a specific tag on a servlet request.

The aggregation type defines how multiple values received in the same interval are aggregated.

Multiple conditions can be concatenated logically. When the condition is evaluated, no operator precedence (AND stronger than OR) is applied:

  • If the first FALSE condition is followed by an AND concatenation, then the complete expression evaluates to FALSE.
  • If the first FALSE condition occurs after an AND concatenation, then the complete expression evaluates to FALSE.
  • If the first TRUE condition is followed by an OR concatenation, then the complete expression evaluates to TRUE.

For example:

  • true AND false OR true — evaluates to false
  • true OR false AND true — evaluates to true
  • true OR false AND false — evaluates to true
  • false AND true — evaluates to false

Threshold configuration

Since filters are based on measures, you need to configure thresholds in the measures you are assigning for filtration. See the Configuration tab - Thresholds section on the Create and configure measures page for more information on how to configure thresholds.

For example:

  • To include all PurePaths that last longer than three seconds, set the upper threshold for the PurePath duration filter to 3 seconds.
  • To include all PurePaths that last less than three seconds, set the lower threshold for the PurePath duration filter to 3 seconds.

You can use measures that provide numeric values as underlying measures for Business Transactions without any special configuration. The only constraint is that you must define a threshold for measures that are used for filtering. Measures that deal with string values require a more sophisticated configuration. See Measure configuration example section below.


The threshold settings of measurements are used both by the Business Transactions filter and by incidents. It is recommended that you create separate instances of measures to use in Business Transactions.


You can add additional related metrics to your business transaction. Add the required measures in this pane. Each measure added to the results produces values if and only if the filter criteria from the previous pane are matched. If the filter criteria are not fullfilled, no metrics are measured. The aggregation type defines how multiple values received in the same interval are aggregated.


The splitting can be used to segment Business Transactions according to the splitting criterion. By default, all newly created Business Transactions are split by application. The maximum number of splittings per Business Transaction is set to 5,000 by default. You can add more than one splitting criterion, for example split by user and by URI.

Baseline settings

Click Violation Detection Settings to configure the maximum deviations for the baseline evaluation. In these are exceeded, a baseline violation incident triggers. See baseline and smart alerting for more information.

Measure configuration example

A Business Transaction is required that filters login transactions of the user demouser. Login validation is performed by the method authenticate, which requires string parameters for username and password with the first parameter providing the username.

Create a measure, based on the authenticate method.

  1. Open the System Profile Preferences dialog box and select the Measures item.
  2. Click Create Measure.
  3. Search for Methods - Argument Value metric, and select it.
  4. In the Analyze and evaluate calls to the following methods pane, select the Manually specify matching pattern check box.
  5. In the Class field, click the magnifying glass icon, to open the Class Browser.
  6. In the Class Pattern field, select the contains criterion, and type login as the search pattern.
  7. In the Agent field, click Pick, and select the Customer Frontend Agent in the Agent Browser.
  8. In the result table, expand the com.dynatrace.easytravel.frontend.login.LoginLogic node, and select the authenticate method.

In the Business Transaction Evaluation/Filter/Splitting Values Specific Atttributes pane, configure the measure to evaluate the occurrence of method calls where the value of the first parameter is demouser.

  1. From the Argument list, select 1 - java.lang.String.
  2. From the Match list, select equals.
  3. In the Value editbox, type demouser.
  4. From the Evaluation list, select occurrence.

Define a threshold for the measure so it can be used for the filter. Set the Exceed of equal threshold as 1, which causes a threshold violation if a method call with the parameter demouser occurs once within a PurePath. This is the behavior required to filter login transactions by the user demouser.

Threshold violations do not automatically trigger incidents, so you don't have to worry about it.

Configured Measure
Configured Measure

Set the configured measure as a filter of a Business Transaction.