To view business transactions for a business application:

  1. In the Applications tab, select an application and then click Business Transactions. The business transaction list shows key metrics for business transactions for the selected time range.


  2. To modify the default view, you can :
    1. Choose to display transactions that belong to business transaction groups.
    2. Select transactions that exceed a configurable average response time.
  3. Click View Options to choose which performance metrics you want to display for business transactions in the list.
  4. Use custom tags to view and filter business transactions, see Tags. Once configured, you can perform the following actions:

    • In View Options, select a tag to view the business transactions associated with that tag. A column appears for the selected tag and it displays the tag value if specified. To filter the business transactions for which a specific tag is not defined, select the value as Untagged for the specific tag filter.

    • Click Filter > Tag Filter and select the tags from the list. It displays the list of business transactions that match the selected tags.

  5. Click to enable the business transaction lockdown. See Business Transactions Overflow.
  6. By default, only business transactions that have performance data in the selected time range appear in the list. You can show inactive business transactions for the time range by modifying the filter view options.
  7. To view which actions you can perform on business transactions, click Actions.
    Actions include:
    • View health rule violations
    • Start a diagnostic session for the transactions
    • Configure thresholds
    • Rename business transactions
    • View Detection Rule
    • Delete Transaction
    • Exclude Transaction
    • View Excluded Transaction
    • Set as background task
    • Mark as Permanent
    • Create a business transactions group
    • Delete business transactions group
    • Export grid data
    • Export detection rules
    • Import detection rules

View and Understand Transaction Entry and Exit Points

When you install an app agent, the agent detects incoming calls and registers transactions based on the default transaction detection rules. Automatic detection rules describe entry points for transactions based on supported frameworks. 

Typically, more than one tier participates in the processing of a transaction. A request to the originating tier may invoke services on:

  • Another instrumented tier – called a downstream tier.
  • Remote services that are not instrumented.

Outbound requests from an instrumented application tier are called exit points. Downstream tiers may, in turn, have exit points that invoke other services or backend requests.

App agents tag exit point calls with metadata describing the existing transaction. When an agent on a downstream tier detects an entry point that includes transaction metadata from another app agent, it treats the entry point as a continuation of the transaction initiated on the upstream tier. This linking of upstream exit points to downstream entry points is called correlation. Correlation maintains the client request context as it is processed by various tiers in your business application.

View Detection Rule

By default, this feature is disabled in the Controller UI. To enable this feature:

  1. Ensure that you are using Java Agent 23.7.0 or later and Controller 23.9.0 or later.
  2. Ensure that the rule.bt.mapping.enabled flag is set to true. See Controller Settings for Detection Rule.

To view the detection rule enabled for business transactions:

  1. Click Business Transactions in the application navigation tree.
  2. Select transactions for which you want to see the detection rules.

  3. Click Actions > View Detection Rule. Alternatively, you can right-click on the transaction for which you want to see the detection rule.
    It opens the Rule Editor window.

    If the View Detection Rule option is greyed out, either the rule.bt.mapping.enabled flag is not enabled or the business transaction is not mapped to the corresponding rule.

Controller Setting for Detection Rule

  1. Log in to the Controller administration console using the root user password.

    http://<controller host>:<port>/controller/admin.jsp

    Use the root user password to access the Admin console when the Controller is installed in single- or multi-tenant mode.

  2. In Controller Settings, search for rule.bt.mapping.enabled and set the Value field to true. 
  3. Click Save. The changes take place after the Agent restarts.