You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've been using the Python OTel lambda layer to trace our lambda functions. We'd like to get the trace/span IDs automatically into the logs so we can connect traces to execution logs.
Since the lambda layer doesn't include opentelemetry-instrumentation-logging, we need to install that package into our lambda dependencies. However, that pulls in opentelemetry-instrumentation and opentelemetry-sdk as transitive deps, and those are in the layer. We end up with two copies of those packages in our lambda bundle, and this opens the potential for conflicts to arise if the instrumentation-logging version gets out of sync with the layer.
Ideally, opentelemetry-instrumentation-logging would be included in the layer directly.
The text was updated successfully, but these errors were encountered:
We've been using the Python OTel lambda layer to trace our lambda functions. We'd like to get the trace/span IDs automatically into the logs so we can connect traces to execution logs.
Since the lambda layer doesn't include
opentelemetry-instrumentation-logging
, we need to install that package into our lambda dependencies. However, that pulls inopentelemetry-instrumentation
andopentelemetry-sdk
as transitive deps, and those are in the layer. We end up with two copies of those packages in our lambda bundle, and this opens the potential for conflicts to arise if theinstrumentation-logging
version gets out of sync with the layer.Ideally,
opentelemetry-instrumentation-logging
would be included in the layer directly.The text was updated successfully, but these errors were encountered: