RuntimeError: Requested component 'otlp_span' not found in entry points for 'opentelemetry_exporter'

[sanderland]

Describe your environment
Python 3.7, poetry virtrual environment

Steps to reproduce
My dependencies include

opentelemetry-instrumentation = "^0.16b1"
opentelemetry-instrumentation-botocore = ">=0.11b0"
opentelemetry-instrumentation-fastapi = ">=0.11b0"
opentelemetry-instrumentation-flask = ">=0.8b0"
opentelemetry-instrumentation-grpc = ">=0.8b0"
opentelemetry-instrumentation-jinja2 = ">=0.8b0"
opentelemetry-instrumentation-psycopg2 = ">=0.8b0"
opentelemetry-instrumentation-requests = ">=0.8b0"
opentelemetry-instrumentation-sqlalchemy = ">=0.8b0"
opentelemetry-instrumentation-sqlite3 = ">=0.11b0"
opentelemetry-instrumentation-starlette = ">=0.11b0"
opentelemetry-api = "^0.16b1"
opentelemetry-sdk = "^0.16b1"

and then run

opentelemetry-instrument python3 src/app.py
in the poetry virtual environment.

What is the actual behavior?
I get the error:

Failed to auto initialize opentelemetry
Traceback (most recent call last):
  File "....venv/lib/python3.7/site-packages/opentelemetry/instrumentation/auto_instrumentation/sitecustomize.py", line 40, in initialize
    initialize_components()
  File "...venv/lib/python3.7/site-packages/opentelemetry/instrumentation/auto_instrumentation/components.py", line 155, in initialize_components
    trace_exporters, metric_exporters = import_exporters(exporter_names)
  File "...venv/lib/python3.7/site-packages/opentelemetry/instrumentation/auto_instrumentation/components.py", line 124, in import_exporters
    exporter_names, "opentelemetry_exporter"
  File "/...venv/lib/python3.7/site-packages/opentelemetry/instrumentation/auto_instrumentation/components.py", line 105, in import_tracer_provider_config_components
    selected_component, entry_point_name
RuntimeError: Requested component 'otlp_span' not found in entry points for 'opentelemetry_exporter'

Additional context
I've searched for otlp or otlp_span packages, but it seems this should just be part of opentelemetry.

[codeboten]

Thanks for raising this issue @sanderland, the entrypoint exists in the package opentelemetry-exporter-otlp which isn't a dependency of the opentelemetry-instrumentation package. There's an issue to decouple the instrumentation from having additional dependencies which will address this issue: #1420

[codeboten]

I should have said that as a workaround you can use the -e none flag when running opentelemetry-instrument to not use the default (OTLP) exporter

[sanderland]

Thanks for raising this issue @sanderland, the entrypoint exists in the package opentelemetry-exporter-otlp which isn't a dependency of the opentelemetry-instrumentation package. There's an issue to decouple the instrumentation from having additional dependencies which will address this issue: #1420

Thanks for getting back to me so quickly. There's probably some improvements to be made to the tutorial and/or error messages.
After checking with colleagues I am going with setting up tracking in the source code instead, since opentelemetry-instrument and uwsgi don't seem to like each other very much.

[github-actions]

This issue was marked stale due to lack of activity. It will be closed in 30 days.

[lzchen]

This issue is resolved.

[anirudhbagri]

I am getting the same error for zipkin!

RuntimeError: Requested component 'zipkin' not found in entry points for 'opentelemetry_exporter

[srikanthccv]

There is no zipkin entry point. It should be either zipkin_json or zipkin_proto.

[anirudhbagri]

Probably we can change this here as well?
https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/sdk-environment-variables.md#exporter-selection

Added a PR