On this page:
To ensure that the HTTP backends detected in your application have meaningful names, your custom configuration will need to take into account the specific format used in your environment.
The format can vary even within a single environment. For example, some backend systems may have hostnames prefixed with ec2storage, which may not be meaningful in naming, while others may use hostnames such as salesforce.com, which may be meaningful.
To account for different formats, you should create a custom rule rather than changing the automatic discovery rule. This lets you apply different rules for different URL formats.
You can then apply specialized approach for each case, as in the following examples:
In some cases, your HTTP backend discovery configuration might consist of a combination of the default rule and custom rules. The following section walks you through a specific example.
For example, when all the HTTP backends for a tier or application have a similar format, such as a prefix like "ec2storage", you can generate the right name and the correct number of backends to monitor by editing the automatic discovery rule. Doing this enables you to monitor the key performance indicators (KPIs) that are of most interest to you.
Consider an application with the following HTTP URLs:
http://ec2-17:5400/service1 http://ec2-17:5450/service2 http://ec2-18:5400/service1 http://ec2-18:5450/service2
In this case, measuring performance based on host name wouldn't be useful, since the IP addresses are transient and all performance numbers would be irrelevant after the IP addresses recycle. Instead, you can monitor by service name by avoiding the use of Host and Port properties and using only the URL property, as follows:
From the segment options drop-down list, select Use the first N Segments.
The important URL segment is for the "create" service, so your configuration is the same as in the previous screen shot.
Enter "/" slash for the Split Delimeter.
Use a similar technique to strip out some segment of the URL, such as a user name as in the following URLs:
Once you change the configuration, delete all HTTP backends. When the agent rediscovers the backends with the new configuration, the flow map shows only the service backends.