Vishwesh Bankwar

@reyang - This is tracked with https://github.com/open-telemetry/opentelemetry-dotnet/issues/5533. I think we should close this one as the failures are not just confined to `OpenTelemetry.Instrumentation.AspNetCore.Tests.BasicTests.AddAspNetCoreInstrumentation_BadArgs`

@stevejgordon It would be good to get this clarification from spec itself. Spec does not outline how this conflict should be handled.

@TylerHelmuth `OpenTelemetry.Instrumentation.AspNetCore` and `OpenTelemetry.Instrumentation.Http` details are correct in the table. For `OpenTelemetry.Instrumentation.AspNet` - Please ask the question on https://github.com/open-telemetry/opentelemetry-dotnet-contrib since it is part of that repo. For `OpenTelemetry .NET Automatic...

@ezhdn Is this what you are trying to achieve? https://github.com/open-telemetry/opentelemetry-dotnet/tree/main/docs/metrics/customizing-the-sdk#rename-an-instrument

@sjrules - It looks like your issue is specific to elastic and not related to OpenTelemetry API/SDK? Could you please clarify? @stevejgordon - Would you be able to help here?

@Yun-Ting Could you take a look?

> Confirming the end result here: > > > 1. OTLP Exporter Options: Opt-in. > > All of the work planned for this issue stays as opt-in, correct? That is...

> ``` > internal const string StatsBeat_ConnectionString_NonEU = ""; > internal const string StatsBeat_ConnectionString_EU = "EU-ConnectionString"; > ``` > > one with angle bracket and one doesn't.. i wonder how...

@davidelettieri - Thanks for reporting this. However, I am not able to repro using your example. I can see the logger.LogInformation("Sample log message"); getting logged successfully.

@davidelettieri - Able to repro this now, Thanks!. Will work on fixing missing logs issue. Note that error you see is due to the way ASP.NET Core is logging (needs...