Srikanth Chekuri

The `OTEL_EXPORTER_OTLP_PROTOCOL` is not supported because we have separate packages for the each protocol. ``` FastAPIInstrumentor.instrument_app(app) ``` This alone doesn't produce the telemetry. Are you using auto-instrumentation or did you...

Did you use the `opentelemetry-instrument` command?

What is `opentelemetry-launcher`? We don't have any such package from official OpenTelemetry. Here is the getting started guide that will help you understand overall concepts https://opentelemetry.io/docs/instrumentation/python/getting-started/. And here is the...

@pankdhnd is this still an issue?

>Overriding of current TracerProvider is not allowed There can only be one global tracer provider and `opentelemetry-instrument` already set one so if you try to set again in your code...

Is this still an issue? Please use the `insecure` init arg or the newly added env for insecure jaeger collector deployments. Feel free to re-open if you still run into...

I mention in the second part of the comment how to pass the exporter as an argument and use env if you have to change things like endpoint etc... And...

I assume you are using the auto instrumentation. When you use it with auto instrumentation, yes, that's the expected way to set the exporter. Since it already sets the global...

Leighton, You are confusing the `Emitter` and `EmitterProvider`. The `Emitter` equivalent is `Tracer`/`Meter` and we don't have flush operation for them. The proposed change in the spec and this issue...

>LoggingHandler class to take in an additional log_emitter_provider arg replace the `log_emitter` arg with provider instance and use it.