These flow maps appear in several of the built-in dashboards depicting different information according to the data context:

Cross-Application

Displays exit calls between applications within the monitored environment. This pattern of calls is known as cross-application flow.

Application

Displays the topology and activities within an application. It displays metric values across all business transactions in the application for the selected time range.

• For example, the application flow map displays calls per minute; average response time for calls made to databases and remote services; and business transaction errors per minute. These metrics are based on all calls made from a specific tier to a database or remote service across all business transactions.
• When an application is one of several in a one-app-per-service architecture, business transactions can represent service endpoints. For these applications, the flow map displays a Cross-BT Hovercard that shows calls to upstream and downstream business transactions which represent endpoints of other services.

Tier and Node

Displays metric values across all business transactions for the subset of the application flow related to the selected tier or node.

Business Transaction

Displays the activity for a BT. The Start label indicates the tier where the transaction starts (the originating tier). This flow map shows metrics that are calculated based on all executions of the BT during the selected time range.

Snapshot

Displays the metrics associated with a single snapshot specific to a particular execution of the transaction.

Splunk AppDynamics shows cross-application flow in other flow maps where appropriate. For example, a tier flow map shows correlation when there are exit calls from the tier to another instrumented application.

Context can determine the meaning of what flow maps represent. Consider the average response time (ART) for calls to a database.

• In the context of an application, ART averages all calls to the database occurring within the application. Suppose that the application flow map shows that ART for those calls is 20 milliseconds.
• In the context of a BT, ART represents the average execution time for the BT as a whole. Suppose that in a BT within the same application, the database gets called twice each time the BT executes. In the BT flow map, ART represents the average duration of a pair of database calls, meaning that ART is 40 milliseconds.