-
Notifications
You must be signed in to change notification settings - Fork 144
import aws_xray_sdk.core
attempts to establish session
#273
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Adding to @lorengordon comments on Python import profile using Python Tuna to find out where the slower calls are -- X-Ray SDK accounts for 75% of Lambda function import time in this hello world example |
Nice! And that botocore.session is almost 50%! 👀 |
Hi @lorengordon, Thanks for opening an issue. I think this initialization code resulting in creating |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs in next 7 days. Thank you for your contributions. |
Bad stale bot |
It feels a little odd for a library to establish a session on import. Is that truly necessary, or would it be possible to gate that setup on an explicit call to an xray class/method?
I only discovered the session is being setup because I happened to have an incorrect/null AWS_PROFILE configured locally, while testing a logging config using the
aws-lambda-powertools-python
library. I opened an issue there, but it seemed more appropriate for the xray team.The text was updated successfully, but these errors were encountered: