Where does "WebTransaction/ASP" come from?

There is an old ticket, but seems it does not answer my question.

Thanks

@wshao1

In general:

  • If the app is an asp.net app and the endpoint is an aspx endpoint then “ASP” categorizes the transaction as ASP.

  • If the app is an asp.net app and the endpoint is not an aspx endpoint then “ASP” means the transaction code executed some of the agent’s asp.net instrumentation but did not execute a code path, say a MVC/WebApi controller, which would have given the transaction a more specific based name.

  • If the app is asp.net core then “ASP” means the request entered the asp.net middleware pipeline but the request didn’t execute the agent’s MVC/WebApi instrumentation which would have given the transaction a controller based name.

Are you asking about the specific WebTransaction/ASP/MvcHandler case? That would mean the agent saw that MvcHandler was called but (for some reason) a controller was not actually called. Maybe some sort of error occurred before that could happen (you could look at the response.status attribute of Transaction events to check this). Here are the methods the agent instruments in order to pick up MVC transactions in an asp. net app:

Does that help?