To view business transactions for a business application:
Click Business Transactions in the application navigation tree. The business transaction list shows key metrics for business transactions for the selected time range.
To modify the default view, you can :
choose to display transactions that belong to business transaction groups.
select transactions that exceed a configurable average response time.
Click View Options to choose which performance metrics you want to display for business transactions in the list.
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.
To view which actions you can perform on business transactions, click Actions. Actions include:
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 AppDynamics 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.
