NET (Agent, Installation)

cancel
Showing results for 
Search instead for 
Did you mean: 

Monitoring IIS single page application which is served by WCF service

Highlighted

Hello,

 

We have a single page application that has been installed in the directory \client. It makes POST calls to the URL which is served by WCF handler. The handler is called via RESTService.svc file. In web.config file is setting:

 

<serviceHostingEnvironment aspNetCompatibilityEnabled="true" multipleSiteBindingsEnabled="true" />

 

so, the call should go via ASP.NET pipeline and should be seen as ASP.NET transactions. Problem is that only WCF monitoring sees transactions and finds only those BTs which makes an actual serving for all URLs. In this case, all BT's goes under a few RESTService.xxx. If I disable WCF monitoring and enable ASP.NET monitoring, nothing can be seen. ASP.NET monitoring can't find any BT's. BT's should be get monitored according to the URL. We are not using EUM.

 

How the match rules should be set up in order to see transactions according to URL? What for is the ready-made match rule "ASP.NET WCF Activation Handler" ? What about "class name" option in the ASP.NET match rule?

 

I have written about the same problem in a thread

https://community.appdynamics.com/t5/NET-Agent-Installation/WCF-calls-in-Asp-net-monitoring/m-p/3622...

 

With regards,

Esko Jaakkola

 

Tags (2)
Monitoring IIS single page application which is served by WCF service