Description
Describe your environment
Python 3.8 AWS Lambda function with the AWS Distro for Open Telemetry layer aws-otel-python38-amd64-ver-1-9-1:1. Using automatic instrumentation by setting AWS_LAMBDA_EXEC_WRAPPER=/opt/otel-instrument.
Steps to reproduce
Pip install opentelemetry-distro, opentelemetry-exporter-otlp, opentelemetry-instrumentation-boto3sqs, and opentelemetry-instrumentation-botocore.
Add arn:aws:lambda:us-west-2:901920570463:layer:aws-otel-python38-amd64-ver-1-9-1:1 lambda layer in SAM.
Run lambda function.
I've uploaded a reproducible example here: https://github.com/hooverdc/poc-boto3sqs
What is the expected behavior?
No RuntimeError.
What is the actual behavior?
Traceback (most recent call last):
File "/opt/python/opentelemetry/instrumentation/auto_instrumentation/sitecustomize.py", line 116, in initialize
_load_configurators()
File "/opt/python/opentelemetry/instrumentation/auto_instrumentation/sitecustomize.py", line 109, in _load_configurators
raise exc
File "/opt/python/opentelemetry/instrumentation/auto_instrumentation/sitecustomize.py", line 105, in _load_configurators
entry_point.load()().configure(auto_instrumentation_version=__version__) # type: ignore
File "/var/task/opentelemetry/sdk/_configuration/__init__.py", line 273, in configure
self._configure(**kwargs)
File "/var/task/opentelemetry/sdk/_configuration/__init__.py", line 289, in _configure
_initialize_components(kwargs.get("auto_instrumentation_version"))
File "/var/task/opentelemetry/sdk/_configuration/__init__.py", line 233, in _initialize_components
trace_exporters, metric_exporters, log_exporters = _import_exporters(
File "/var/task/opentelemetry/sdk/_configuration/__init__.py", line 201, in _import_exporters
for (exporter_name, exporter_impl,) in _import_config_components(
File "/var/task/opentelemetry/sdk/_configuration/__init__.py", line 170, in _import_config_components
raise RuntimeError(
RuntimeError: Requested component 'otlp_proto_grpc' not found in entry points for 'opentelemetry_metrics_exporter'
Additional context
This appears to be an issue with the 0.32b0 release? I have a similar lambda using the 0.30.b1 release without this issue.