Cijo Thomas
Cijo Thomas
I like option1 - CategoryName, Scopes, EventId etc are ILogger specific concepts, and by OpenTelemetry .NET SDK preferentially treating `ILogger`, they are part of LogRecord. Since they are not a...
^ agree with this "attack" plan :)
Somewhat related/similar is - OTel .NET decided to use `Activity` from runtime, instead of own class. But in our exporters, we try to only export what is required by OTel...
You may be looking for this https://github.com/open-telemetry/opentelemetry-dotnet-contrib/tree/main/src/OpenTelemetry.Instrumentation.Runtime
> I think all these metrics can be consumed through DiagnosticListeners API Not really... Probably you are referring to some runtime metrics being published via EventCounters? For that, yes you...
https://github.com/open-telemetry/opentelemetry-dotnet-contrib/tree/main/src/OpenTelemetry.Instrumentation.Runtime is to get specific metrics published by .NET Runtime components (like GC, JIT etc) https://github.com/open-telemetry/opentelemetry-dotnet-contrib/tree/main/src/OpenTelemetry.Instrumentation.EventCounters is for subscribing to *any* EventCounters. Could be custom event counters, or even the...
No ETA yet. At the minimum, this PR (https://github.com/open-telemetry/opentelemetry-dotnet/pull/2107) must be finished. We are also discussing if Extensions.Hosting should be part of this repo or should be "lift and shifted"...
Update: As the focus is mostly on shipping Metrics SDK/.NET 6 support, this is delayed, at least till early 2022. There were a large number of queries and interest about...
@utpilla will look at this early next Month, and give an update.
AddSource is meant to add ActivitySources. I dont think this usage is correct. Take a look at the example asp.net core app, and see if that is what you are...