Srikanth Chekuri

Yes, I was wondering if there is way to continue run tests for 3.6 but that doesn't seem possible.

@ofek The PR that dropped support for py36 is merged. Please resolve the conflicts and we can get this merged.

Does this apply to the logging? Unlike metrics and traces, logging doesn't have an API. In case tracing/metrics user adds new instrumentation code and may need the no-op. With logging...

https://github.com/open-telemetry/opentelemetry-python/blob/0b4f247e9d401e94ec77f72ddfcf917298ea27e8/exporter/opentelemetry-exporter-prometheus/setup.cfg#L53-L55 I think it was discussed to name it `opentelemetry_metric_reader ` for Prometheus since it is an implementation of `MetricReader`. We will probably have to update the configuration to code...

There is none for the auto instrumentation right now.

Discussion during 11th Aug call. We are probably going to change the way we load the (metric) exporters for auto instrumentation which works regardless of the implementation type (push exporter/...

All your commits will be squashed before merging.

Feel free to pick some new issues. I will be happy to help you.

I remember using Gunicorn with auto instrumentation and see it emit traces while debugging some issue.

If you are running with k8s operator auto instrumentation you should use HTTP exporter for this stated [reason](https://github.com/open-telemetry/opentelemetry-operator/blob/main/autoinstrumentation/python/requirements.txt#L2). ``` export OTEL_TRACES_EXPORTER=otlp_proto_http export OTEL_EXPORTER_OTLP_ENDPOINT=http://otel-collector:4318 ```