Extract route on ASP.NET for Performance Transaction Name about sentry-dotnet HOT 3 OPEN

To give some context here:
Our ASP.NET HttpContextExtension sets the transaction's NameSource to URL and does not extract the route.

from sentry-dotnet.

Additional Context

• Routing differences between ASP.NET MVC and ASP.NET Core

It's worth noting we might have some challenges with the default route (which is often the only route used by many applications) which is:

        routes.MapRoute(
            name: "Default",
            url: "{controller}/{action}/{id}",
            defaults: new { controller = "Home", action = "Index", id = "" },
            constraints: new { id = "\\d+" }
        );

Literally everything maps to "{controller}/{action}/{id}" as the routename when using this convention based routing configuration. We could assume that the controller name and action name are safe to share (i.e. not PII) and so pass those through but leave the id masked... which might give us more useful groupings if people are using the default route.

When people are not using the default route it's really hard to know which parts of the route are safe to store in the SentryEvents and which bits are potentially PII though... so we'd probably just have to leave everything masked in those cases (i.e. everything sharing the same route, where it's not the default route, would be grouped by Sentry on the server).

At least, that's one possible implementation.

from sentry-dotnet.

Relates to: getsentry/sentry-docs#7866

from sentry-dotnet.