-
Notifications
You must be signed in to change notification settings - Fork 109
Description
Describe the bug
I have OTEL layer auto instrumented lambda in AWS region us-west-2 which uses OTEL layer -
arn:aws:lambda:us-west-2:901920570463:layer:aws-otel-python-amd64-ver-1-29-0:2
The traces were correctly being sent to OTEL collector -> dynatrace until 21st July, but we noticed no tracing after that.
I checked the logs for CloudWatch and started seeing this error as attached here
log-events-viewer-result (8).csv
We tried updating the lambda layer to the latest version [arn:aws:lambda:us-west-2:901920570463:layer:aws-otel-python-amd64-ver-1-32-0:2] but still see same issue.
log-events-viewer-result (9).csv
OTEL layer is trying to read a symbol inside the sdk - std_to_otel which is already fixed in the later versions
Answer form OTEL team - open-telemetry/opentelemetry-python#4715
This breakage was part of this open-telemetry/opentelemetry-python#4649
otel-lambda already bumped the dependencies: https://github.com/open-telemetry/opentelemetry-lambda/blob/main/python/src/otel/otel_sdk/requirements.txt to the latest ones
Probably mix of dependencies issue?
distro = entry_point.load()()
--
| 2025-08-13T10:31:40.000Z | ~~~~~~~~~~~~~~~~^^
| 2025-08-13T10:31:40.000Z | File "/var/task/importlib_metadata/__init__.py", line 221, in load
| 2025-08-13T10:31:40.000Z | module = import_module(self.module)
| 2025-08-13T10:31:40.000Z | File "/var/lang/lib/python3.13/importlib/__init__.py", line 88, in import_module
| 2025-08-13T10:31:40.000Z | return _bootstrap._gcd_import(name[level:], package, level)
| 2025-08-13T10:31:40.000Z | ~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
| 2025-08-13T10:31:40.000Z | File "<frozen importlib._bootstrap>", line 1387, in _gcd_import
| 2025-08-13T10:31:40.000Z | File "<frozen importlib._bootstrap>", line 1360, in _find_and_load
| 2025-08-13T10:31:40.000Z | File "<frozen importlib._bootstrap>", line 1331, in _find_and_load_unlocked
| 2025-08-13T10:31:40.000Z | File "<frozen importlib._bootstrap>", line 935, in _load_unlocked
| 2025-08-13T10:31:40.000Z | File "<frozen importlib._bootstrap_external>", line 1026, in exec_module
| 2025-08-13T10:31:40.000Z | File "<frozen importlib._bootstrap>", line 488, in _call_with_frames_removed
| 2025-08-13T10:31:40.000Z | File "/opt/python/opentelemetry/distro/__init__.py", line 23, in <module>
| 2025-08-13T10:31:40.000Z | from opentelemetry.sdk._configuration import _OTelSDKConfigurator
| 2025-08-13T10:31:40.000Z | File "/opt/python/opentelemetry/sdk/_configuration/__init__.py", line 39, in <module>
| 2025-08-13T10:31:40.000Z | from opentelemetry.sdk._events import EventLoggerProvider
| 2025-08-13T10:31:40.000Z | File "/opt/python/opentelemetry/sdk/_events/__init__.py", line 23, in <module>
| 2025-08-13T10:31:40.000Z | from opentelemetry.sdk._logs import Logger, LoggerProvider, LogRecord
| 2025-08-13T10:31:40.000Z | File "/opt/python/opentelemetry/sdk/_logs/__init__.py", line 16, in <module>
| 2025-08-13T10:31:40.000Z | from opentelemetry.sdk._logs._internal import (
| 2025-08-13T10:31:40.000Z | ...<8 lines>...
| 2025-08-13T10:31:40.000Z | )
| 2025-08-13T10:31:40.000Z | File "/opt/python/opentelemetry/sdk/_logs/_internal/__init__.py", line 32, in <module>
| 2025-08-13T10:31:40.000Z | from opentelemetry._logs import (
| 2025-08-13T10:31:40.000Z | ...<5 lines>...
| 2025-08-13T10:31:40.000Z | )
| 2025-08-13T10:31:40.000Z | ImportError: cannot import name 'std_to_otel' from 'opentelemetry._logs' (/var/task/opentelemetry/_logs/__init__.py)
| 2025-08-13T10:31:40.003Z | Failed to auto initialize OpenTelemetry
| 2025-08-13T10:31:40.003Z | Traceback (most recent call last):
| 2025-08-13T10:31:40.003Z | File "/opt/python/opentelemetry/instrumentation/auto_instrumentation/__init__.py", line 130, in initialize
Steps to reproduce
Auto instrumented Lambda python function.
What did you expect to see?
Should be able to see traces in Dynatrace without lambda layer error
What did you see instead?
Import error
Environment
Describe any aspect of your environment relevant to the problem.
Additional context
Add any other context about the problem here.