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
As discussed in SIG (August 1, 2024) we agreed to remove aws-lambda instrumentation from the list of default instrumentation used in bootstrap. Instead of requiring everyone to opt-out, AWS Lambda users should opt-in.
More context: we had some cases of users facing issues in aws-lambda instrumentation even if they are not running anything on aws lambda, forcing them to have to uninstall the instrumentation package or disable the instrumentation using OTEL_PYTHON_DISABLED_INSTRUMENTATIONS environment variable: #2744 #2769
The text was updated successfully, but these errors were encountered:
As discussed in SIG (August 1, 2024) we agreed to remove aws-lambda instrumentation from the list of default instrumentation used in bootstrap. Instead of requiring everyone to opt-out, AWS Lambda users should opt-in.
More context: we had some cases of users facing issues in aws-lambda instrumentation even if they are not running anything on aws lambda, forcing them to have to uninstall the instrumentation package or disable the instrumentation using
OTEL_PYTHON_DISABLED_INSTRUMENTATIONS
environment variable:#2744
#2769
The text was updated successfully, but these errors were encountered: