Configure Node Properties for MVC Transactions

You can configure custom MVC transaction naming using node properties. This table describes how to configure node properties for MVC transactions based on the type of entry point.

Note: The node property supports: MVC 3, MVC 4, and WebAPI transactions.
Type of Entry PointName Business TransactionsTransaction Naming Configuration

ASP.NET hosted in IIS ( aspdotnet-mvc-

To name business transactions using the Controller and Action values

Register the aspdotnet-mvc-naming-controlleraction true

To name business transactions using the Area and Controller values

Register the aspdotnet-mvc-naming-controllerarea true

To include all three component values (Controller, Action, and Area) in business transaction names
  1. Register both node properties
  2. Configure the ASP.NET transaction naming to use three URI segments instead of two (default)

See Automatic Transaction Discovery Rules.

ASP.NET Core on the Full Framework( aspdotnet-core-

To name business transactions using the URIRegister both of these node properties with a value = false
  • aspdotnet-core-naming-controllerarea **
  • aspdotnet-core-naming-controlleraction
To omit the Area value from your transaction names

Register the aspdotnet-core-naming-controllerarea false

.NET Agent for LinuxTo use MVC Area, Controller, URI, and Action in business transactions nameRegister the aspdotnet-mvc-naming-controlleraction node property with a value = true

To register a new node property, see App Agent Node Properties.

After you modify any transaction naming configuration, and traffic to the previously registered business transactions terminates, you can delete the old business transactions.