Cijo Thomas

Looked at this more closely, and we don't have public API risk with this. The method used by Logger to get a list of processors form the provider is not...

@ibigbug Are you facing issues without `tracing-opentelemetry` as well? If the issue is when `tracing-opentelemetry` is involved, then not much we can do in this repo. The final answer depends...

> @cijothomas the thing is there is something you can do, if for every version you release you have a table of the versions of each ecosystem crate that is...

I see.. Thanks for clarifying. Is the below reply from @lalitb good enough? i.e we already release all crates together. (sorry about missing zipkin crate by mistake). Is that not...

@xd009642 Please let us know if you have more suggestions on this. We just unified the version across all crates in this repo

> I think this API behavior is very unintuitive: in most cases the user wants to add resource attributes, not remove the default attributes yes, agree. Will look at addressing...

https://github.com/open-telemetry/opentelemetry-rust/pull/1674/files seem to be fixing it. If not ,lets fix it separately.

On 7/9 SIG, we also discussed the need to make AnyValue and Value Enum variants consistent. The former provides conversion for lower size integers, but the latter does not. We...

Thanks for reporting the issue. Meter attributes are not supported yet on Prometheus exporter. We are currently prioritizing core api/stable sdk + OTLP exporters only, it'll be a while when...

See https://github.com/open-telemetry/opentelemetry-rust/compare/main...lalitb:thread-runtime?expand=1 also to get some ideas about solving same/similar problems.