MartinDotNet

The most common cause for this is that the trace is coming in from an external source, so it's inheriting a trace from an external source and none of those...

Since we have the stable instrumentation for AspNetCore with the required attributes, I'm not sure whether there is anything that we should be doing with this ticket? @cijothomas would you...

@dpk83 there's a couple of point here that I think are interesting, I've done very specific analysis on this along side the benchmarks in the repo. Your analysis of the...

This is an ongoing task to optimize and therefore this isn't a tracking issue. If you have specific areas and suggestions to improve them, I'd suggest they're split out into...

This looks like it's not something we're planning on, or can be, fixed, so I'm closing this as Not Planned.

From reading up, it seems like we're not planning anything in Otel for this, so we can close this issue right? /cc @cijothomas @Wraith2

> This is an expected churn and was https://github.com/open-telemetry/opentelemetry-dotnet/discussions/4686 well in advance. Who is that you're expecting to have seen that issue and catered for it? The thousands of people...

> Who is promising that this package is stable, and there won't be breaking change? The nuget is marked pre-release, and the [readme.md](https://github.com/open-telemetry/opentelemetry-dotnet/tree/main/src/OpenTelemetry.Instrumentation.AspNetCore#aspnet-core-instrumentation-for-opentelemetry-net) clearly states its non-stable status. I think...

@farlop Have you tried using the latest versions? I suspect this is an old issue.

So this looks like MAUI is not outputting the right information, perhaps using a custom HTTP client that doesn't generate use the diagnostic listeners properly. @bijington anything you can tell...