We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OpenTelemetry.Instrumentation.AspNetCore
In AspNetCoreTraceInstrumentationOptions we have Filter configuration but
Filter = context => { var endpoint = context.GetEndpoint(); //Endpoint is null here ... };
Expected
AfterRoutingFilter = context => { var endpoint = context.GetEndpoint(); //Endpoint is !not null! ... };
Why? Working with Endpoint Metadata is a standard in the Asp community. So we can achieve something same we have with AllowAnonymous
// Decompiled with JetBrains decompiler public static TBuilder AllowAnonymous<TBuilder>(this TBuilder builder) where TBuilder : IEndpointConventionBuilder { ref TBuilder local = ref builder; if ((object) default (TBuilder) == null) { TBuilder builder1 = local; local = ref builder1; } local.Add((Action<EndpointBuilder>) (endpointBuilder => endpointBuilder.Metadata.Add((object) AuthorizationEndpointConventionBuilderExtensions._allowAnonymousMetadata))); return builder; }
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Uh oh!
There was an error while loading. Please reload this page.
Component
OpenTelemetry.Instrumentation.AspNetCore
Is your feature request related to a problem?
In AspNetCoreTraceInstrumentationOptions we have Filter configuration
but
What is the expected behavior?
Expected
Why?
Working with Endpoint Metadata is a standard in the Asp community.
So we can achieve something same we have with AllowAnonymous
Which alternative solutions or features have you considered?
Additional context
No response
The text was updated successfully, but these errors were encountered: