Hi Team, I have a question regarding reverse (circular) HTTP exit call topology support in the AppDynamics .NET agent. Scenario: Two .NET applications running on different machines Application A makes a blocking HTTP call to Application B Before sending its response, Application B makes a blocking HTTP call back to Application A Both HTTP calls complete synchronously (no async / fire-and-forget) This creates a circular topology . Question: Does the AppDynamics .NET agent support discovering and visualizing this reverse / circular HTTP call topology correctly (both exit calls and entry calls) in the flow map / service topology? If not fully supported: Is there any recommended configuration or correlation setting? Are there known limitations with reverse exit calls in .NET agents? Looking forward to your guidance. Thanks in advance. ... View more

  Hi Team, I am trying to understand whether AppDynamics supports visualizing bidirectional (reverse) HTTP exit calls between two .NET applications within the same Application Flow Map. My setup Two machines: Machine A – Remote1 Machine B – Remote2 Both machines: Have AppDynamics .NET Agent installed Are reporting to the same AppDynamics Controller Belong to the same AppDynamics application Communication pattern: Remote1 → Remote2 (HTTP request) Remote2 → Remote1 (HTTP callback / reverse HTTP call) Observed behavior in AppDynamics The Application Flow Map shows only one direction Either Remote1 → Remote2 Or Remote2 → Remote1 The reverse call is executed successfully in the application, but it does not appear as a second directional dependency in the topology. 📎 Attached Image 1: Shows the AppDynamics Application Flow Map with only a single directional dependency between Remote1 and Remote2. Observed behavior in Dynatrace (for the same flow) Using the same application logic and traffic pattern, Dynatrace shows bidirectional communication: Remote1 → Remote2 Remote2 → Remote1 Both directions are visible simultaneously in the service topology. 📎 Attached Image 2: Shows Dynatrace service flow with bidirectional arrows between the two services. My question Does AppDynamics support visualizing bidirectional HTTP dependencies between the same two tiers/services in a single Application Flow Map? If yes: Are there any specific requirements or constraints (BT type, synchronous vs async calls, correlation rules, thread handling, etc.)? If no: Is this a known design limitation of the AppDynamics topology model? Is the expected AppDynamics behavior to collapse reverse calls into a single dependency, even when two HTTP calls occur in opposite directions? Any clarification or official documentation reference would be very helpful. Thank you. Dynatrace result appdynamics result ... View more