Display Regular HTTP Requests as Services/Tiers
The applications that we are monitoring use external services via 'standard' HTTPRequest (e.g., REST) - no SOAP involved. These calls are not displayed in the Transaction Flow or Web Services dashlet. This is a little annoying, since REST services are getting more and more common. Sure, there's no endpoint defined like there is in SOAP, but there's still a server and a URL...
This is DT 5.6, so I am hoping that behavior has changed in 6.1. 
What I would like to see is a standard HTTPRequest be treated as a web service if the remote server is not part of the PurePath. So that the server name, at least, will appear as an external tier, and the server/URL will appear as a web service definition.
One issue that could be a problem is the structure of the URL's, since you have to tell if the URL contains a dynamic element (object id) that is not actually part of the service definition/endpoint.
So - the Web Services Dashlet only shows "real" Web Service calls that use some of the Web Services STandard Frameworks. But - all HTTP-based Requests should show up in the Web Requests DAshlet. Open that dashlet. Then open the context menu and select Show -> All. That will show you all Web Requests in all PurePaths and not just those from your Entry Points. Let me know if that helps
Plus - yeah - 6.1 is definitely the way to go
Yeah, that's helpful. I don't like that everything is lumped together, but it gives me the information I need.
Thanks!
I'm still trying to figure out how I knew nothing of that menu option in the dashlet.
Thanks andreas.grabner@dynatrace.com - We do see the HTTPUrlConnection in the PP, we just don't see that remote URL appear in the Web Services dashlet. 5.6 is looking a little old now, so we'll see what 6.1 does.
Hi David
That should actually work. We already identify any outgoing HTTP Request as External Call. I am however not exactly sure when this feature was introduced. It was definitely in 6.0 but I kind of thought it was already part of 5.x -> but I might be wrong here.
You do see these outgoing calls in the PurePath though - do you?
