Provide a way for users to define a Transaction name (Avoid Unknown Route )

[bruno-garcia]

Currently, unless the route is known via endpoint routing or MVC, the SDK creates transactions named Unknown Route. This is suboptiomal as there are many cases where the route should just. be the path (i.e: Static files).

The problem with defaulting to that is that it's possible some middleware is handling things dynamically like /something/GUID and those would break the grouping of transactions (it should be /something/{id} as a transaction name instead of a new transaction for each GUID).

We need to provide an API for users to define what should be defined as a transaction and what should fallback to Unknown Route.

[lucas-zimerman]

My suggestion would be to alter the interface https://github.com/getsentry/sentry-dotnet/blob/main/src/Sentry.AspNetCore/ISentryRouteName.cs
to

namespace Sentry.AspNetCore;

public interface ISentryRouteName
{
    string? GetRouteName(HttpContext context);
}

Then add an extension to SentryAspNetCoreOptions where the user is able to register his class.
Lastly, we could check here

sentry-dotnet/src/Sentry.AspNetCore/SentryTracingMiddleware.cs

Line 119 in 41cf450

if the user registered the extension and invoke the following code:

    httpContext.Features.Set<ISentryRouteName>(UserSentryRouteName);

[bruno-garcia]

@lucas-zimerman not sure I follow. How much effort would it be to have a PoC for this so we can have an idea?
This keeps coming up. And even on my experience with nugettrends.com it's rather annoying to have those when I'd like to see the static files it served, for example.

Additionally, how would we support other frameworks that themselves would have routes? Like servicestack

[mattjohnsonpint]

Completed in #1421