Skip to content
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

Elastic stack related plugins should take into account proxy environment variables #14206

Closed
oserde opened this issue Oct 29, 2023 · 1 comment · Fixed by #14207
Closed

Elastic stack related plugins should take into account proxy environment variables #14206

oserde opened this issue Oct 29, 2023 · 1 comment · Fixed by #14207
Labels
feature request Requests for new plugin and for new features to existing plugins

Comments

@oserde
Copy link
Contributor

oserde commented Oct 29, 2023

Use Case

We use telegraf agent within a corporate network, but have some elasticsearch servers in the cloud. In order to connect to internet things, we need to go through an HTTP/HTTPS proxy. Right know, elasticsearch, elasticsearch_query, kibana, and logstash plugins are not taking into account standard proxy variables such as HTTP_PROXY, HTTPS_PROXY and NO_PROXY, and there is no specific config attribute to go through a proxy neither.

Expected behavior

By setting http_proxy or https_proxy environment variables, telegraf plugins should send http or https request through a proxy

Actual behavior

These plugins do not take into account http proxy variables.

Additional info

No response

@oserde oserde added the feature request Requests for new plugin and for new features to existing plugins label Oct 29, 2023
@powersj
Copy link
Contributor

powersj commented Oct 30, 2023

next steps: review PR, however we do need to be backwards compatible as Sven's review points out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Requests for new plugin and for new features to existing plugins
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants