Default Actions for managed Elastic Stack (ESS/ECE/ECK)

[peterschretlen]

Describe the feature:

Kibana should provide default connectors for Cloud that are tied to cloud account notification settings.

Actions should also be aware of certain details like Cloud ID, instance identifiers, and console URL, to allow things like deep link to the cloud console to scale a deployment for example.

There are a few open question, the first step in this issue is to provide recommendations on:

• how should cloud/ECE/ECK configure actions? config file, web service, etc?
• how can deployment metadata be provided to alerts and actions

Describe a specific use case for the feature:

A notional example: Kibana provides a built in cloud email action type. This action does not user SMTP, but calls an incoming webhook exposed by cloud. Connectors can be configured via kibana.yml and will be created at startup, providing ready-to-use connectors when you first use Kibana.

[elasticmachine]

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

[pmuellr]

It's not clear if there's more work we need to do on the alerting side for this, given preconfigured connectors and support for emailing through the ESS proxy. @arisonl ???

[mikecote]

Closing due to lack of activity.