Configure .NET Agent HTTP Client Correlation and HTTP Backend URL Path Naming

Path groups are named groupings of web service HTTP client requests that you define in terms of an HTTP backend URL path prefix.
Path groups
 are named groupings of web service HTTP client requests that you define in terms of an HTTP backend URL path prefix.
HTTP Client Correlation
.NET agent client correlation starts with a page request from server to server. An instrumented server makes a client call to another server or an agent or a public web service. Therefore, the calling server is known as the 
, although technically the server is not actually a client. The server is instrumented to see outgoing request calls. When a call goes to another server that is also instrumented by an agent, then the call can be correlated.
These three .NET libraries are used in .NET agent HTTP client correlation framework:
  • System.Net.HttpWebRequest
  • System.Web.WebClient
  • System.Net.Http.HttpClient
HTTP Backend Path Group Naming
You can configure a set of .NET HTTP Backend path group properties to monitor the performance of outgoing HTTP queries that your  .NET applications make. The HTTP backends data displays as standard BlamePoint metrics under the Backends|WebService at {protocol}_//{host}:{port} Investigator node. Together these properties capture the HTTP method and the query parameters being used in transaction traces. You can configure error snapshots to be generated whenever an HTTP 4XX or 5XX response code is received.
These introscopeAgent.profile HTTP backend path group properties work together:
With this configuration, the default HTTP backend paths display in an HTTP backend path group. Typically HTTP backend paths display under the Metric Browser 
Backends|WebService at {protocol}_//{host}_{port}|Paths
To capture and group more path details for the various URLs, configure the URL path groups in the agent profile.
Using HTTP Backend Path Groups
The metrics for each path group are aggregated under the 
Backends|WebService at <
 node in the Investigator metric browser tree. By default, all HTTP backend URL paths are assigned to the 
 group. With path groups, you can determine how many requests are invoked from the HTTP backend. You can then diagnose performance problems.
The following example shows three HTTP backend URL paths as they would display in the metric browser tree:
Backends|WebService at http_//host_port|Paths|alphaHTTPClientPost
Backends|WebService at http_//host_port|Paths|betaHTTPClientGet
Backends|WebService at http_//host_port|Paths|Default
This example shows how three path groups are defined in the agent profile:
Define Keys for Path Groups
 Delimiter characters in the agent profile define a list of the keys of all the path groups. The key for a path group is referenced in other property definitions that declare an attribute of the path group.
Each entry has two properties that are used to define the path and match output results as follows:[
The [
] entries are used to locate the named property. The 
 value corresponds with the 
 property as shown:
You can define path groups so some paths fall into multiple groups. In this situation, the order in which you list the keys for the path groups in the 
 property is important. Be sure that the path group with the narrower membership precedes the path group with broader membership.
Define Membership of Each Path Group
 property specifies a pattern against which the path prefix of a path is matched. The matching defines which requests fall within the path group.
Example: Map a Group Key to a Path Prefix
This property definition assigns all requests in which the path portion of the path starts with 
 to the path group whose key is 
Requests that match the specified pathprefix include:
You can use the asterisk symbol (*) as a wildcard in 
Define the Name for a Path Group
 property determines the names under which response time metrics for a path group are generated.
Typically, the<key>.format
 property is used to assign a text string as the name for a path. The following example causes metrics for the path group with key 
 to appear in the metric browser tree under the name 
Alpha Group
: Group
(Optional) Advanced Naming Techniques for Path Groups
You can derive a path group name from request elements such as the protocol, or from a substring of the request path. This section describes advanced forms of the<key>.format 
Use a Substring of the Request Path as a Path Group Name
You can organize statistics for a path group under names that reflect a substring of the path portion of request paths. Define<key>.format 
as shown:
 is the index of the first character, and 
 is one greater than the index of the last character. String selection operates like the 
 method. For example, for the following setting:
With this URL:,sessionid/pageid
Statistics would appear under: 
The path grouping works only on the path part of the URL. In the previous example it is: 
Use a Delimited Portion of the Request Path as a Path Group Name
To organize statistics for a path group under names that reflect a character-delimited portion request path, define the
 property as shown:
 character delimits the segments in the path. The 
 value is the index of the first segment to select, and the 
 value is one greater than the index of the last segment to select. For example, given this setting:
Statistics for the requests of this form:,sessionid/pageid
Appear under the metric node 
Follow these rules:
  • Delimiter characters count as a segment. In the previous example, the delimiter characters is the forward slash (/).
  • Segment counts start at 0.
  • Path grouping works only on the path part of the URL. In the previous example, the path part of the URL is 
The segments as delimited by the slash character in the path example are:
, 1=
, 2=
, and 3=
You can specify multiple delimiters as necessary. For example, given this setting:
Statistics for requests of the form that is shown in the previous example appear under the 
 node. The segments as delimited by the slash and the comma in the path example are:
, 1=
, 2=„
, 4=
, and 5=
Limit the Number of Unique Backend Path URL Group Metrics
You can use the 
 property to to limit the number of unique backend path group URL metrics that the .NET agent creates. When the number of new backend path groups reaches the set value, metrics for new backend path group URLs display in the Metric Browser. They display under the 
Backends|WebService at {protocol}_//{host}_{port}|Paths|
 node. This property helps to prevent metric explosions.
To collect meaningful metrics from the 
Backends|WebService at {protocol}_//{host}_{port}|Paths
 node, set up backend path groups that are relevant to your deployment.
Follow these steps:
  1. Open the IntroscopeAgent.profile in the <Agent_Home> directory in a text editor.
  2. Go to the URL Grouping Configuration section.
  3. Configure the 
    The default is 5 backend path group URLs.
  4. Save and close the file.
    No managed application restart is needed.
Backend Path Group Naming
These backend path group properties work together when all are set to their default introscopeAgent.profile settings as shown:
With this configuration, the default backend paths display in a backend path group. The group is named for and located two segments after the protocol in the backend path. 
For example, typically backend paths are listed under the 
Backends|WebService at {protocol}_//{host}_{port}|Paths
 node. When the number of backend path groups that are created across all the .NET applications reaches the 
 setting, any new backend paths display under the 
Backends|WebService at {protocol}_//{host}_{port}|Paths|