Support scheme field when creating a Threshold alert with a Webhook action

[cjcenizal]

Per the docs, the Watcher API supports a scheme field when creating a webhook action, which accepts "http" and "https" as values. We need to update the UI and serialization logic to support this field.

[elasticmachine]

Pinging @elastic/es-ui

[cjcenizal]

This problem has also been reported on the forums: https://discuss.elastic.co/t/simple-watcher-webhook/201471/5

[michaeljohnbennett]

in the interim how can I work around this? I'm posting to telegram webhook but it's failing as its HTTPS only?

Will I need to get the request json and push it manually via postman or the like to update?

[alisonelizabeth]

Hi @michaeljohnbennett! There is currently no workaround via the threshold alert. However, you can create an advanced watch through the Watcher UI and specify the scheme as part of the watch JSON. You may also go to DevTools in Kibana, open Console, and create the watch using the Watcher API.

Here is some more information:

• https://www.elastic.co/guide/en/kibana/current/watcher-ui.html#watcher-create-advanced-watch
• https://www.elastic.co/guide/en/elasticsearch/reference/current/watcher-api-put-watch.html
• https://www.elastic.co/guide/en/elasticsearch/reference/current/actions-webhook.html

[brotherat]

Another detail about this issue is that when a webhook, created via json file, with setting “"scheme": "https",” in it, is being edited via the GUI, it automatically changes the value of “scheme” to “http”

[alisonelizabeth]

Thanks @brotherat! We are actively working on a fix via #53757.