Deepak Modi

To add: - This benchmarking is done without any exporter (Adding exporter will likely reduce the throughput even further) - The requests also didn't have any baggage. I suspect requests...

> There is much more done to create a full activity, including things like trace propagation and also filling out additional properties too. That's not to say that it isn't...

> If you aren't using baggage, try doing this... // When the default propagator is just w3c we respect the work AspNetCore does instead of calling the SDK logic. //...

> Sdk.SetDefaultTextMapPropagator(new TraceContextPropagator()); @CodeBlanch I tried this and it's actually causing a different activity everytime. All the exported chained activities have different traceId.

Created open-telemetry/opentelemetry-dotnet#4326

This is an important issue so checking for the status here. It is on track for getting fixed in the upcoming stable OpenTelemetry release, right?

@reyang This is an important ask and I was expecting this to be addressed in 1.5 stable release. We have been pushing services across our org to adopt distributed tracing...

Oh so you are saying this will only be available when AspNetCore instrumentation becomes stable. What are the timelines for that? Based on the timelines we will have to evaluate...

Okay looks like there is some problem on my side and I am not able to understand the statements properly. Let’s simplify things: Could you please share the ETA when...

> @dpk83 I believe you also mentioned the need to know how many metrics etc are being dropped, due to dimensioncap/other reasons. Yes, exactly. When metrics are dropped due to...