Does AppDynamics .NET Agent Support Reverse / Circular HTTP Exit Call Topology?

[chaplin20260107]

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.