Mikel Blanchard

> Is there a way to opt out? `OTEL_DOTNET_EXPERIMENTAL_ASPNETCORE_DISABLE_URL_QUERY_REDACTION` PR: https://github.com/open-telemetry/opentelemetry-dotnet/pull/5532/files#diff-eef1a6fbb9155013c4a21ba1f3da8ade5f0ac7e08d23bd761575b4ecd70ac86aR36-R42

@dpk83 There is a lot of work that has to be done in the AspNetCoreInstrumention to support OTel baggage because .NET doesn't do it. > The requests also didn't have...

Great ideas to improve baggage! Mind spinning up an issue to track that? For the case here where baggage isn't being used (probably very common case) what might be more...

@ViktorHofer's [comment](https://github.com/dotnet/runtime/issues/86667#issuecomment-1560445498): `...we can't mark the package as deprecated as it is part of the supported netstandard1.x dependency graph.` Seems to be a supported scenario?

> 2. Have all OpenTelemetry.ResourceDetectors.* packages have a root namespace of OpenTelemetry.Resources > 3. Have all OpenTelemetry.ResourceDetectors.* packages provide .Add{detector_name}Detector extension methods on top of ResourceBuilder and targeting namespace OpenTelemetry.Resources...

> Also, keep in mind the namespace is Resources, not Resource. Agree the namespace should be `Resources` (plural). I went with singular form for the package name because that seems...

Thanks @mowies I assigned the issue to you. I have no idea what to use 🤣 Checking the other repos around OTel sounds like a great idea to me.

@shenyutong10086 If you are interested in working on this please start with a proposal.

@Kielek I updated the description. But feel free to create individual issues if you want. This was more for just tracking things being added in .NET 9 we need to...

We discussed this on the SIG today. Opened #5935 for Console. Some questions about what to do for Zipkin, opened a dedicated issue to track that: #5936