I think the confusing part is that client-side web requests (e.g. a call of get URLConnection.getInputStream) are handled in a different way as server-side web requests (e.g. a call of Servlet.doPost):
For a client-side web request the complete URI is tracked as a whole string (e.g. https://bankpayments.serv.dteco.com/QueryAccts). For a server-side web request we only track path and query of the URI (e.g. /paymentsAdapter/makePayment). To be more precise, in case of Java Servlets it's the return value of the following method:http://docs.oracle.com/javaee/6/api/javax/servlet/http/HttpServletRequest.html#getRequestURI().You can see the difference in the "Argument" column of the PurePath tree - every client-side web requests shows a complete URI , while the first (server-side) web request shows only the path + query part.
To define a measure that matches path/query and host name, please do the following:
1. Adapt the "Servlet" sensor properties to capture the HTTP Host header
2. Use a "Web Request - Header Value" measure as filter measure in your BT
Servlets is for Java applications. My customer has the same need but we run mostly .NET
Can I instead configure the ASP.NET sensor pack and add the same there? i.e. source = Request Header, and Attribute = Host.