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
In 7.14.x it is possible to run Elastic Agent via proxy. There is a flag: --proxy-url
However, currently this flag isn't documented. Note that proxy mode was actually broken in 7.14.0 and fixed in 7.14.1. Please see: #27114.
Note also we observed the following:
Elastic Agent appears to configure various Beats to send logging/metric data to Elasticsearch. In the configuration file for Filebeat (which is created by the Elastic Agent), it doesn't appear to have any configuration for using the proxy. From a quick glance it appears that the "enroll --proxy-url" option does nothing for the Beats.
By trial and error, we've gotten it to work using --proxy-url to enroll the agent and environment variables (HTTP_PROXY, HTTPS_PROXY, NO_PROXY) so the Beats are also aware of the proxy settings. As we've used the RPM file to install the Elastic Agent (which runs as a Systemd service), we've had to configure Systemd to provide these Environment Variables to the elastic-agent.service.
This must also be documented; having said that, perhaps Agent should handle this when doing automatic configuration?
The text was updated successfully, but these errors were encountered:
In 7.14.x it is possible to run Elastic Agent via proxy. There is a flag:
--proxy-url
However, currently this flag isn't documented. Note that proxy mode was actually broken in 7.14.0 and fixed in 7.14.1. Please see: #27114.
Note also we observed the following:
This must also be documented; having said that, perhaps Agent should handle this when doing automatic configuration?
The text was updated successfully, but these errors were encountered: