Cijo Thomas
Cijo Thomas
Yes, it is similar to https://github.com/open-telemetry/opentelemetry-rust/issues/2753 We cannot stabilize Otel Tracing API with these APIs exposed. (A lot of special casing to support `tracing-opentelemetry` actually). Hopefully @bantonsson's work will allow...
Yes okay to keep them now to not break `tracing-opentelemetry`. But I don't think we can delay 1.0 indefinitely either. Need to see if `tracing-opentelemetry` maintainers can commit a timeframe...
@demurgos Thanks in advance for your patience! I am clearing my backlog and will get to this soon!
@lalitb Can you help continue this?
Closing this, as we have a PR already open to make this happen : https://github.com/open-telemetry/opentelemetry-rust/pull/2374
https://github.com/open-telemetry/opentelemetry-rust/issues/2386 is opened to track fixing issues like this. Keeping the issue open until the fix is in for Traces.
BatchProcessor and PeriodicReader are modified to use own thread and do blocking calls from within it. OTLP/SDK Docs are updated to show the working combinations and non-working ones and integrations...
AddMeter(ABC.*).AddMeter(XYZ.*) etc - are these not sufficient? You can read the list of MeterNames from IConfiguration and feed it to AddMeter([]metername) - won't that work? The ILogger filter capability is...
Can be closed with https://github.com/open-telemetry/opentelemetry-specification/pull/4188
Looks like this is an issue specific to Azure Monitor, as it uses a sampler that does not follow the parent's sampling decision. The `Filter` option in Asp.Net core propagates...