Permissions

The View Sensitive Data permission, In combination with the Configure Transaction Detection permission, enables the use of Live Preview and Business Transaction Discovery features to stream live data from your application.

Live Preview

For Java and .NET environments, you can use interactive live preview tools to find business transaction entry points:

Business transaction discovery sessions stream live data from the node to the Controller UI to help you make instrumentation decisions. These sessions display transactions based on all transaction detection rules active for the node.

For certain types of entry points, custom match rule live preview enables you to preview transactions based on applying a single transaction detection rule on a node.

Business transactions within the context of the Live Preview, called transient transactions, do not persist after the Live Preview ends. Business transaction discovery sessions let you apply or discard rule changes when you end the session. Custom match rule live preview rules apply after you save the rule.

Some transient transactions may invoke exit calls to the same node where the Live Preview session is running. In certain cases, the agent may discover additional transient transactions and uninstrumented code on the downstream segment:

The exit call and corresponding entry point are automatically discovered exit and entry points like HTTP or Web Service.

Rare cases of custom activity in-process calls.

Manage Transaction Detection Rules

To customize transaction detection rules in the Controller UI, go toConfiguration > Instrumentation. From the Business Transactions list, you can also click Configure to quickly access Transaction Detection settings.

You apply transaction detection rules to tiers using the flexible scope configuration model. From the Transaction Detection tab, you can manage rules as follows:

Manage rules for individual scopes on the Scopes tab.

Manage rules application-wide on the Rules sub-tab. The Rules sub-tab also shows you the tiers where rules are applied and according to which scope.

View or modify the rules for specific tiers on the Tiers sub-tab.

To modify an existing rule, you can double-click it to display the Rule Editor. Click +/Add to define a new rule.

If you upgraded your business application to AppDynamics 4.3 or newer, you can view and customize transaction detection rules for existing business applications using the legacy hierarchical configuration model.

Transaction Detection Rule Priorities

AppDynamics app agents apply transaction detection rules of the same type in the following order of precedence:

Rule priority from highest to lowest. A priority of 0 is the lowest priority possible.

To view the default order of transaction detection rules for a tier

For Java and .NET, you can set the check-bt-excludes-early node property to "true" toconfigure the app agent to evaluate custom match exclude rules before custom match include rules. This is a node-based configuration and does not affect the display order of rules in the Controller UI.