Proxy support for action type slack, nodemailer, etc?

[mikecote]

Is there a generic http proxy setting? nodemailer will want smtp proxy (???) or maybe socks?

[elasticmachine]

Pinging @elastic/kibana-stack-services (Team:Stack Services)

[pmuellr]

A quick peek through NPM shows some popular proxy libraries

• https://www.npmjs.com/package/proxy-agent
• https://www.npmjs.com/package/socks-proxy-agent
• https://www.npmjs.com/package/socks

The first two are related - the first calls the second - and the first seems to cover "http and https proxies" and not just SOCKS proxies. I'm guessing that watcher supports just SOCKS, but I haven't peeked yet.

The first two also work by supplying a special agent on the http request, which makes them a little easier to use, but only if agent is something you can send into our http request library.

[mikecote]

Added note: the goal of this issue is for all the action types to work when using a proxy.

[timroes]

I would like to cc @elastic/kibana-platform on this one. It feels for me like we should start having a general proxy setting, and a client on the serverside available that takes care of proxying requests, so every code that needs to make outbound requests take care of it, and you don't need to configure a separate proxy for all the separate applications.

Leaving aside whether we need to find an intermediate solution for alerting I would be curious to hear the platform teams thoughts on this.

[mshustov]

We have an issue open to support this functionality #41960 without ETA though. Do you have an idea when you need it?

[mikecote]

@restrry We are aiming to have a solution by the time our server side APIs become GA in 7.10.

[mshustov]

@joshdover FYI and our 7.10 planning