cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Not a customer? Start a free trial

Click the Start a free trial link to start a 15-day SaaS trial of our product and join our community as a trial user. If you are an existing customer do not start a free trial.

AppDynamics customers and established members should click the sign in button to authenticate.

NET (Agent, Installation)

Monitoring IIS single page application which is served by WCF service

Esko.Jaakkola
Builder

Monitoring IIS single page application which is served by WCF service

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)
By replying you agree to the Terms and Conditions of the AppDynamics Community.
Monitoring IIS single page application which is served by WCF service
0 REPLIES 0