In the AppDynamics model, business applications usually represent a complete application environment. However, it is possible that different business applications share services or infrastructure components.
The cross application flow map lets you see those dependencies and points of contact between business applications in the Controller. This topic describes the cross application flow map.
To view the cross-application flow map, the user must have the account-level View Business Flow permission.
The Applications tab in the AppDynamics Controller UI provides several views of the business applications in your account: a card view, list view, and flow view. To access the cross application flow map, click the flow view link in the tab.
To see the cross application flow click the View All Applications link on the Controller UI Home page. The page appears as follows:
In the context of a given business application, the call to another application is considered an exit call. If the other application is an AppDynamics-instrumented business application, the call is shown as cross application flow. For an example, see the All Applications Flow Map on Flow Maps. All users of one application can see correlated applications on the flow map. However, to drill into metrics and snapshots for a correlated application, a user must be a member of a role with view permissions to the correlated application. See Roles and Permissions
If your environment includes business applications from multiple accounts on one or more Controllers, you can view correlation between those applications with the federated cross application flow.
You can hide backend components, applications, or queues in the right-clicking menu for the component on the cross-application flow map.
For applications monitored with the Java Agent, you can exclude a node from being resolved to a cross-application flow by setting the following app agent node property to false:
This property must be set in the downstream application and prevents calls from external apps registering as cross-application flows.
You may choose to do this, for example, if you wanted the cross application call to be represented as a backend call in the calling applications flow map—and metric scheme—rather than as a call to another application. This ensures that metric data reflecting interactions with the tier in the external business application are retained as backend call metrics.
The node property