We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
See meta issue for the description and details:
The text was updated successfully, but these errors were encountered:
It looks like we're already doing this, by coincidence. We create separate connection pools where we fetch the cloud metadata:
apm-agent-python/elasticapm/utils/cloud.py
Line 43 in d19c5ff
Line 95 in d19c5ff
Line 134 in d19c5ff
In contrast, the connection pool used in the transport explicitly sets up a ProxyManager if the HTTP[S]_PROXY environment variable is set.
ProxyManager
HTTP[S]_PROXY
apm-agent-python/elasticapm/transport/http.py
Lines 124 to 129 in d19c5ff
@basepi agree to close this as completed? Or should we add comments in utils/cloud.py to not use ProxyManager there, just in case?
utils/cloud.py
Sorry, something went wrong.
beniwohli
No branches or pull requests
See meta issue for the description and details:
The text was updated successfully, but these errors were encountered: