By default, when an app agent detects a URI request, it names the business transactions using the first two segments of the URI. For example, consider the following URI for a checkout operation in an online store: http://acmeonline.com/store/checkout.

The agent names the business transaction "/store/checkout" and assigns all requests that match that URI to the "store/checkout" business transaction.

If the first two segments of the URI do not contain enough information to effectively identify the business transaction in your environment, you can edit the automatic discovery rule to name the transaction based upon the URI and its context. Alternatively, you can create a custom match rule to specify a name.