Srikanth Chekuri

@Zoharos thanks for taking a stab at it. There was a change in proto since 0.15.0 because of renaming `InstrumentationLibrarySpans` to `ScopeSpans` https://github.com/open-telemetry/opentelemetry-proto/releases/tag/v0.15.0. Which version of `@opentelemetry/exporter-trace-otlp-*` are you using?

We will probably upgrade in next major release

@huahuayu It's not practical to adopt some new protocol and it's not about writing some program. OTLP is already stable and everything is built on top of it. FYI, You...

Not fully addressed

I wanted to try out this feature but realised not supported for different backends. I can take a stab at this if nobody is already working on it.

I agree. On the other hand, how to enforce that the exporter implementation must have `force_flush`? If it's an abstract method then the processor can expect all implementations to have...

Looks like we don't have the `@abstractmethod` for the [`SpanExporter`](https://github.com/open-telemetry/opentelemetry-python/blob/main/opentelemetry-sdk/src/opentelemetry/sdk/trace/export/__init__.py#L50-L77) base class methods so this new addition with nop is fine. Do you know how base classes are divided into...

Did you mean providing them with entrypoint style? One could configure the SDK samplers with env today.

> It would be ideal to get the control over both the logging level and the logging format. I think you are mixing different things here. The `OTEL_LOG_LEVEL` is for...

https://opentelemetry.io/docs/instrumentation/python/#status-and-releases