Cijo Thomas

eg: `provider.with_batch_exporter(exporter-with_unsupported_client_like_request)` should return a Result. The Err should clearly indicate the reason for failure.

I was referring to the `.build()` method to detect invalid combination and return Result. Related to this is https://github.com/open-telemetry/opentelemetry-rust/pull/2654 which only does Exporter specific one. This issue is about the...

> Do you already have any concerns to change build() to return Result? No. I prefer build() returns Result. The part that needs design is what Error enum it would...

Spec allows this now, https://github.com/open-telemetry/opentelemetry-specification/pull/4188 So this issue must be un-stale

Another showed up during community call today: How to do shutdown correctly! The following does not proceed to call remaining shutdowns, if one before fails. That needs to be fixed...

Can you explain what is the end goal here? I understand this is an old issue, but want to make sure we grasp the issue well.!

Thanks for the explanation! This is not something covered by the spec, and hence it is unlikely we'll give an explicit support.

From SIG meeting on 5/14 Make force_flush return Vec! of Results from each processor (logs,traces), reader (metrics). The order in which processors are invoked are not guaranteed. (explicitly document this)...

The best suggestion I can give at the moment is to see if you can switch to OTLP Exporter given OTLP is now accepted by Prometheus. We are not actively...

https://github.com/open-telemetry/opentelemetry-dotnet/issues/5859 Needs to be done for this.