https://community.splunk.com/t5/Splunk-AppDynamics/Does-AppDynamics-NET-Agent-Support-Reverse-Circular-HTTP-Exit/m-p/757747#M12006 <P>&nbsp;</P><P>Hi Team,</P><P>I have a question regarding <STRONG>reverse (circular) HTTP exit call topology</STRONG> support in the <STRONG>AppDynamics .NET agent</STRONG>.</P><P><STRONG>Scenario:</STRONG></P><UL><LI><P>Two .NET applications running on different machines</P></LI><LI><P>Application A makes a <STRONG>blocking HTTP call</STRONG> to Application B</P></LI><LI><P>Before sending its response, <STRONG>Application B makes a blocking HTTP call back to Application A</STRONG></P></LI><LI><P>Both HTTP calls complete synchronously (no async / fire-and-forget)</P></LI></UL><P>This creates a <STRONG>circular topology</STRONG>&nbsp;.</P><P><STRONG>Question:</STRONG></P><P>Does the AppDynamics .NET agent <STRONG>support discovering and visualizing this reverse / circular HTTP call topology</STRONG> correctly (both exit calls and entry calls) in the flow map / service topology?</P><P>If not fully supported:</P><UL><LI><P>Is there any recommended configuration or correlation setting?</P></LI><LI><P>Are there known limitations with reverse exit calls in .NET agents?</P></LI></UL><P>Looking forward to your guidance.</P><P>Thanks in advance.</P> Thu, 29 Jan 2026 06:58:01 GMT chaplin20260107 2026-01-29T06:58:01Z https://community.splunk.com/t5/Splunk-AppDynamics/Does-AppDynamics-NET-Agent-Support-Reverse-Circular-HTTP-Exit/m-p/757747#M12006 <P>&nbsp;</P><P>Hi Team,</P><P>I have a question regarding <STRONG>reverse (circular) HTTP exit call topology</STRONG> support in the <STRONG>AppDynamics .NET agent</STRONG>.</P><P><STRONG>Scenario:</STRONG></P><UL><LI><P>Two .NET applications running on different machines</P></LI><LI><P>Application A makes a <STRONG>blocking HTTP call</STRONG> to Application B</P></LI><LI><P>Before sending its response, <STRONG>Application B makes a blocking HTTP call back to Application A</STRONG></P></LI><LI><P>Both HTTP calls complete synchronously (no async / fire-and-forget)</P></LI></UL><P>This creates a <STRONG>circular topology</STRONG>&nbsp;.</P><P><STRONG>Question:</STRONG></P><P>Does the AppDynamics .NET agent <STRONG>support discovering and visualizing this reverse / circular HTTP call topology</STRONG> correctly (both exit calls and entry calls) in the flow map / service topology?</P><P>If not fully supported:</P><UL><LI><P>Is there any recommended configuration or correlation setting?</P></LI><LI><P>Are there known limitations with reverse exit calls in .NET agents?</P></LI></UL><P>Looking forward to your guidance.</P><P>Thanks in advance.</P> Thu, 29 Jan 2026 06:58:01 GMT https://community.splunk.com/t5/Splunk-AppDynamics/Does-AppDynamics-NET-Agent-Support-Reverse-Circular-HTTP-Exit/m-p/757747#M12006 chaplin20260107 2026-01-29T06:58:01Z