When you develop an ASP.NET Core application, a pipeline is built by connecting the configured middleware components together.

By default (for example, when you re-use the standard template application startup code), you do not have to define how to build the pipeline or the sequence of middleware components in this pipeline. Everything works as defined. For applications with more complex processing demands, you would typically modify the middleware pipeline and consider how the .NET Agent instruments ASP.NET Core applications. See middleware pipeline information from the Microsoft site.

The .NET Agent can instrument this middleware pipeline at different points along the pipeline. Each instrumentation option provides advantages and disadvantages:

• Resource invoker instrumentation
• Endpoint instrumentation
• HTTP instrumentation
• MVC routing instrumentation