Cijo Thomas

Discussed on SIG meeting 7-July. Agree to make this in -contrib repo, as this sampling is not part of official spec. Will migrate to main repo if this becomes part...

@hananiel Assigning this to you since you mentioned interest in contributing this!

This is not part of the API/SDK. This will likely be hosted in the -contrib repo, but no timelines yet. (One good thing is, we are not likely blocked by...

I believe this would be part of SDK spec. I am also interested in getting a hook in the Metric SDK to get raw metric events and also aggregated metric...

> OpenTelemetry instrumentation libraries by default export their data [Instrumentation Libraries](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/glossary.md#instrumentation-library) provide instrumentation. It has no control on where the telemetry is exported. So I think the statement "OpenTelemetry instrumentation...

> If ActivitySource will support all then/currently supported versions of .NET, we should consider it. A proof-of-concept PR would be appreciated (I assume there are preview releases of some kind...

Just to clarify - ActivitySource/Activity API is for tracing , and not for metrics. Things like BytesSent, etc are metric, which require a metric API. .NET has `EventCounter` API to...

@stebet Thanks! To instrument, you won't need OpenTelemetry dependency, right? You can use 5.0.0 of DiagnosticSource. (Also OpenTelemetry will release 1.0.0 in

https://github.com/open-telemetry/opentelemetry-dotnet/tree/main/src/OpenTelemetry.Exporter.OpenTelemetryProtocol#troubleshooting Follow the troubleshooting steps and can you get the logs, so we can figure out whats going on?

If OTel.Instrumentation.AspNetCore is used - then it should have worked in all versions. It does the job of extracting Baggage from "baggage" header.