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

[watcher] Provide a noproxy setting for the ability to avoid proxy for specific hosts with Watcher if proxy is configured #60703

Open
geekpete opened this issue Aug 5, 2020 · 1 comment

Comments

@geekpete
Copy link
Member

geekpete commented Aug 5, 2020

Provide the equivalent of a noproxy / NO_PROXY setting to allow scenarios where a proxy allowing only external destinations is configured to avoid traversing the proxy for internal or specific addresses that the proxy would not allow to pass through or that the user prefers not to go via the proxy for.

For example where you want to use external actions like PagerDuty/Slack requiring a proxy but also want to use Web Hooks actions against local or internal network addresses that cannot be reached if going via the configured proxy Watcher uses or preferably shouldn't go via the proxy.

So a complimentary Watcher setting to the xpack.http.proxy.host one:
https://www.elastic.co/guide/en/elasticsearch/reference/current/notification-settings.html

eg:
xpack.http.noproxy.host

@geekpete geekpete added >enhancement :Data Management/Watcher Team:Data Management Meta label for data/management team needs:triage Requires assignment of a team area label labels Aug 5, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-features (:Core/Features/Watcher)

@jimczi jimczi removed the needs:triage Requires assignment of a team area label label Sep 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants