Open gregkalapos opened 2 years ago
Python is in a good place at the moment, judging by the (lack of) feedback. That said, it would be fairly trivial to align if we decide to do so. I don't have strong feelings on alignment, might be easier to keep it technology-specific.
Go does have proxy support, I've updated the description. I haven't seen enough requests to know if we should align, but if we do I'd prefer to use the de-facto standard names HTTP_PROXY
, HTTPS_PROXY
, NO_PROXY
.
Summary from agent weekly:
MUST
, so no need for agents with existing implementations to change anything).
Some agents have a configuration to set a proxy to the http client which reports to APM Server.
Current status:
ELASTIC_APM_
+proxy_address
,proxy_headers
,proxy_password
,proxy_port
,proxy_username
HTTP_PROXY
/HTTPS_PROXY
,NO_PROXY
- these are generic configs, not only for the agent. If a user wanted to use different proxy settings for the agent and the underlying app, that could be problematic.It seems these settings are very different across agents. Some agents don't have this config (e.g. .NET) and it came up that we should support it in those agents as well.
Questions:
ELASTIC_APM_HTTP_PROXY
(happy to take another name, the point of the suggestion is to have a single config with a string value that takes a URL with all the URL address rules)