NET (Agent, Installation)

cancel
Showing results for 
Search instead for 
Did you mean: 

Monitoring IIS single page application which is served by WCF service

Monitoring IIS single page application which is served by WCF service

Hello,

 

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

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

so, call should be 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 BT:s which makes actual serving for all url:s. In this case all BT's goes under 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 setup 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 same problem in thread

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

 

With regards,

Esko Jaakkola

 

Monitoring IIS single page application which is served by WCF service