We have a .NET application that makes many backend calls to external endpoints. Unfortunately many of them are not discovered by automatic backend detection. I've also tried setting up custom exit points but that didn't help. We are not making async calls. Any help would be appreciated. Thanks!
Hi Morgan,
Please provide more details on the backend calls made by your code. The default backend detection would detect most of the common calls and usually async calls are the ones that will not be detected by default. The other possibility for a dropped backend is when there is a backend explosion(>300 backends - this typically happens when there are many calls to HTTP external calls and the backend detection is not configured well).
-Thiru
It sounds like our issue is the backend explosion issue. How can I configure backend detection so it still detects these calls?
Hi Morgan,
If you calling external HTTP endpoints, please delete your existing detected backends and try grouping them by configuring Backend detection to use only the Host and port or a segment of the URL. This will help in limiting the number of backends. Please let us know if you need more info.
Please find the link to the documentation for Backend detection configuration below.
https://docs.appdynamics.com/display/PRO39/Configure+Backend+Detection+for+.NET
-Thiru
Thanks for the info. I believe many of our backend calls are currently automatically discovered as WCF. Will it work as HTTP anyway?
Hi Morgan,
You can do the same for WCF exits as well. Please edit your WCF automatic discovery rules.
-Thiru
The suggested solution did not help.
Hi Morgan,
Sorry to hear that. Thanks for opening the support ticket. We will analyze this further and troubleshoot the issue.
-Thiru