By default, Splunk AppDynamics uses the host name and port number to detect and name HTTP backends. This may be suitable in many cases, however, when your microservices, containers or serverlets are managed by an API gateway or portal, backend services communicating with a client or with each other cannot be correctly mapped to the proper tiers unless you edit automatic discovery to use a portion of the query string or use HTTP custom discovery rules to uniquely name them. Splunk AppDynamics recommends you create a custom HTTP backend discovery rule in this case.

The following screenshots provide an example configuration.

Here we choose Match Conditions to describe the API gateway host, in this case, api.appdynamics.com.

This screenshot also shows where we choose to use the First 3 segments, using '/' as both the split and merge delimiters.

Configuring the HTTP Backend Discovery Rule as above detects backend metrics and reports them under a business transaction name that begins with api.appdynamics.com followed by the first three segments of the URL of the transaction, such as api.appdynamics.com/api/catalog or api.appdynamics/api/payment. Transactions matching the configured HTTP discovery rule are recognized as individual backends even when they share the same host name and port number. These transactions can be mapped to different tiers so you can analyze the metrics of the transactions that occur behind the API gateway.