Monitoring WCF .NET application
I have seen a couple of the other WCF posts on here and I am not finding information to help me with my issue - so I figured I would start a new thread.
We have an application made up of multiple tiers - WebServers(IIS) -> Frontend Servers(.NET WCF) -> Process/Preview Servers(.NET WCF) -> Output Servers(.NET WCF) -> Print Servers
We are seeing the Web Requests from the Web Servers showing up in the purepath dashlet but they only have one or two nodes in them. We have the WCF and Web Requests sensors deployed to the Front end servers, but we are not seeing the connection in the purepath from the Web Request to the Front end servers. If I enable "start purepaths" on the WCF sensor on the Front end servers, I can then see the WCF calls showing up in the purepath dashlet. According to the dev folks, they are using net.tcp as a listening endpoint on the front end servers. Can you give some insight as to what we might be missing? We have gone as far as to instrument all of the custom classes on the front end servers and we still do not see a connected purepath. We are also seeing the same indication for the tiers further down the tree - Process, Output, etc...
Thanks.
Hi. Enabling the .NET WCF Sensor Pack should take care of tracing PurePaths across these runtime boundaries. Our implementation will add a custom property/header on the WCF Message with the name "x-dynatrace". Once this property/header is on the message it should be picked up by the WCF Sensor on the server-side in order to continue the PurePath.
The only explaination I have is that our property/header doesnt make it all the way through. I've seen WCF Apps where custom property/header checks were implemented that removed any custom data from the WCF message that was not known. Could you check with your engineering team whether they have checks like this implmented that would remove our dynaTrace property/header from the message
