For some MVC applications, URI-based naming may not produce meaningful business transaction names. Depending on the URI scheme, it might create many business transactions, pushing you quickly over your business transaction limit and causing most traffic to fall into theAll other trafficbusiness transaction.

For example, consider an MVC application that indicates store locations in the URL as the result of a city location search, such as the following sample URL:

http://myapp.mycompany.com/Bellevue

Based on this URL, Splunk AppDynamics registers a business transaction named /Bellevue. Each search result with a unique city would similarly generate a unique business transaction.

Alternatively, you can configure the agent to identify transactions by the area, Controller, or action name. After you configure the agent to name transactions by Controller and action, the agent identifies the business transaction based on the Controller and action name, in this case, Home/Forbidden Home/Index

In this example, the new business transaction combines search requests for all cities into one transaction, resulting in a more logical unit for measuring application performance.

Similarly, if your application uses areas to logically group Controllers, you can configure the use of area name in the business transaction.

For background information on ASP.NET Routing, see this Microsoft Developer Network article: msdn.microsoft.com/en-us/library/cc668201.aspx