Cijo Thomas

Same issue reported differently: As reported in gitter channel this is an issue if you try to start own activity inside an AspNetCore application without enabling the AspNetCoreInstrumentation.

@alanwest The root of the issue is some libraries (eg: Asp.Net Core) is creating activity irrespective of whether Otel asked is to do so. This is a "by design" behaviour...

The best we can do is to document this behaviour. Tagging this as a documentation issue.

@mitoihs You can use a diff. sampler other than the default ParentBased sampler. This should give you the required solution for you.

The demos could default to AlwaysOnSampler ?

Digging up an old, but I think related to this https://github.com/open-telemetry/opentelemetry-dotnet/pull/1973

Yes! This issue is still open. You can start by looking at the existing tests and identify gaps. The issue description has a link to PR adding basic tests.

> > 1. The current design requires Sorting based on keys. Based on benchmarking, this is the biggest contributor to the hot path. One potential way to improve this is...

@utpilla is looking at implementing the item 1 to avoid sorting costs.

The most critical improvements are already shipped as part of 1.2 itself. Removing this from 1.3 milestone, as it can occur anytime. (1.3 is releasing in May 2022 with other...