This page applies to an earlier version of the AppDynamics App IQ Platform.
For documentation on the latest version, see the 4.4 Documentation.

Skip to end of metadata
Go to start of metadata

Applies to:


Related pages:

If there is a true logical separation among software applications in your environment, you can map them to different business applications in the Controller. AppDynamics maintains the transaction context between the applications using cross application flow. This feature is currently supported for the Java, .NET, Node.js and Python beta application agents.

For example, consider a bank that has two applications: Web Banking and Loans. They are two logically different applications that are developed and maintained by separate teams. However, the Web Banking application makes calls out to the Loans application. In AppDynamics, the calls from the Web Banking application to the Loans application appear as cross application flow.

The following considerations may influence your decision to set up multiple applications with cross application flow:

  • Separate and distinct teams develop and maintain different application components. You want to control application-level visibility between teams.
  • You have a complex environment and your users will benefit from more focused visibility.

Exit calls from one application to another AppDynamics-instrumented application in the same Controller account appear on the flow map. 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 Configure Custom Roles.

A user needs View Business Flow permission to see all the applications in the flow. See Account-Level Permissions in Configure Roles.

  • No labels