'HTTP URL Connection Tagging' sensor not found
Hi,
We are not finding the 'HTTP URL Connection Tagging' sensor in dynatrace version above 4.1. Was this removed in latest versions or replaced with another sensor.
Either way, most of our purepaths are now broken into two where as in earlier version of dynatrace these used to be single purepaths.
Can we know what has changed on this sensor?
Also how do we troubleshoot the purepaths disconnect issue.
-Sreerag
This Sensor was replaced with the JAva Web Request and .NET Web Request Sensor. Make sure that these Sensor Packs are placed and you should be all good again
Hi Andi,
Ours is a Java application all the way to the back end, And we have the 'Java Web Requests' sensor placed.
This is how it is coming in the purepath. When a call is made to the backend java web service a 'getInputStream' node comes in the purepath. but the purepath call tree remains in the same agent group. And all the processing happening in the backend because of this call is in another purepath.
We could look for custom tagging, but it was working ok till we upgraded, custom taging means code change and not code change is one of the biggest advantages of dynatrace. we would like to keep it that way.
-Sreerag
What about the "backend" agent? Is it still instrumented? Do you see any PurePaths that make it to that backend agent?
yes the backend service is also instrumented, but those information are coming in different purepath. (a purepath starting at the backend).
Sreerag, what are the classes of the bracketing classes on both sides of the call? In particular any HTTPClient calls. I've seen the PP break if there was some less-popular or perhaps custom coded wrapper on the calling side.
Rob
Welcome the
Dynatrace Community Forums
Check out the Forum User Guide and Forum Guidelines to learn how to get started.Community Member of the Month
August 2017
Announcing Dynatrace's Community Member of the Month for August 2017, Rick B.! Click here to read more! 
