Use the URL Path in a Detection Rule

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. This enables you to monitor the KPIs that are interested in.

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 would not 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:

  1. Edit the Automatic Backend Discovery rule for HTTP for your agent type. See Backend Detection Rules for details on accessing this pane.
  2. First, select and disable the use of Host and Port.
  3. Then select and enable the property you want to use to uniquely identify the backend. In this case, select URL and check Use URL in the Backend Name.
  4. For the field How will URL be used in the Backend name?, select Use a segment of it.
  5. From the segment options drop-down, select the important URL segment is for the "create" service, so your configuration is the same as in the previous screenshot. Use the first N Segments.
  6. 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: 
    [http://host:34/create/username1]
[http://host:34/create/username2]
  7. 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.