You can correlate the network request events of End User Monitoring (EUM) applications with the business transactions of business applications. The EUM application can be a browser, mobile, or IoT application. The correlation is made between EUM application beacons containing network request event information and instances of business transactions (transaction snapshots). 

This page discusses the general configuration for business translation correlation for EUM applications. For detailed information, including how and what is correlated for each type of EUM application, see the following pages:

Benefits of Correlating Business Transactions

By correlating business transactions with network request snapshots, you can identify potential issues with the backend application that are causing bad user experiences. For example, you might find that a server error or a database query is causing a slow or very slow user experience.

Before You Begin

To correlate business transactions, you are required to do the following:

  1. Purchase licenses for Application Performance Monitoring (APM) and End User Monitoring (EUM).
  2. Instrument a business application with a supported App Agent:
  3. Instrument an EUM application (Browser, Mobile, or IoT application).

If automatic business transaction correlation is not supported for your App Agent, you can manually enable business transaction correlation in the Controller UI.

Business Transaction Correlation Support for App Server Agents

The table below shows the App Agents that have support for correlating business transactions. Automatic correlation support means that business transactions are automatically correlated by default. For manual correlation, you must manually enable business transaction correlation.

App Server AgentType of Correlation Support

Java Agent

Automatic (Java Agent 4.5 and higher)

.NET Agent

Manual

Node.js Agent

Manual

PHP Agent

Manual
Python AgentManual

Access Business Transaction Correlation

To configure business transaction correlation:

  1. In the Application Dashboard, click Configuration User Experience App Integration.
  2. Under the Business Transaction Correlation tab, there are two options depending on the correlation support for your App Server Agents:

Automatic Correlation of Business Transactions

By default, the correlation of business transactions of business applications instrumented with the Java Agent 4.5.0 and higher is enabled.

Under the Business Transaction Correlation tab, you can choose to opt out or filter requests with match or exclude rules.

Opt In to Automatically Correlate Business Transactions

To opt in to have business transactions automatically correlated, you must need to use the Java Agent 4.5.0 and higher. If you are using an older version of the Java Agent, you must upgrade the agent.

For unsupported agents, you need to manually enable business transaction correlation.

Opt Out of Automatic Correlation

If business transaction correlation is enabled by default, you can opt out by doing the following:

  1. In the Application Dashboard, click Configuration User Experience App Integration.
  2. Under the Business Transaction Correlation > Opt Out of Correlation, click opt out of correlation.

  3. From the Opt Out of Correlation dialog, click Opt Out.

Manually Enable Business Transaction Correlation

For App Agents that do not have automatic correlation support, you need to manually enable business transaction correlation.  

To manually enable business transaction correlation:

  1. In the Application Dashboard, click Configuration User Experience App Integration.
  2. Under the Business Transaction Correlation tab, check the Enable Business Transaction Correlation checkbox.

Disable Business Transaction Correlation

To disable business transaction correlation:

  1. In the Application Dashboard, click Configuration User Experience App Integration.
  2. Under the Business Transaction Correlation tab, toggle the Enable button.

Filter Business Transactions for Correlation

You can also specify which business transactions includes or excludes correlation headers. If you do not add request match rules or request exclude rules, all requests have correlation headers by default.

To add a request match or exclude rule:

  1. From Filtering Options, expand Request Match Rules or Request Exclude Rules.
  2. Click Add Rule.
  3. Check the Method to use the default HTTP method GET or select a different HTTP method.
  4. Check the URI checkbox and select one of the matching methods from the dropdown:
    • Starts With
    • Ends With
    • Contains
    • Equals
    • Matches Reg Ex
    • Is in List
  5. (Optional) Click the gear icon to check the NOT checkbox. This condition reverses the results by excluding the requests that match the specified parameters.
  6. Click Add Rule.