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

Cloud monitoring emails in basic #67661

Closed
mikecote opened this issue May 28, 2020 · 6 comments
Closed

Cloud monitoring emails in basic #67661

mikecote opened this issue May 28, 2020 · 6 comments
Labels
estimate:needs-research Estimated as too large and requires research to break down into workable issues Feature:Actions/Framework Issues related to the Actions Framework Feature:Actions NeededFor:Cloud Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@mikecote
Copy link
Contributor

The ability for cloud stack monitoring alerts to send emails in basic license.

@mikecote mikecote added Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels May 28, 2020
@elasticmachine
Copy link
Contributor

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

@pmuellr
Copy link
Member

pmuellr commented Jun 4, 2020

Need more context.

If there is some kind of configuration we could check, I think we could dynamically change the license level of actions. If this is some kind of special environment, where we could install specialized plugins (eg, like I think cloud must be doing), we could potentially key off that somehow.

A "shallow clone" of the existing email action is also possible (reuse all the code, just create a new actionType with a different name/license/etc).

@gmmorris gmmorris added the loe:needs-research This issue requires some research before it can be worked on or estimated label Jul 14, 2021
@YulNaumenko
Copy link
Contributor

YulNaumenko commented Aug 13, 2021

@arisonl, @Kushmaro is it still a requirement?

@Kushmaro
Copy link

Hey @YulNaumenko ! :)

IIRC the rationale for this one was to enable cloud deployments with the email functionality even if the cloud account is on a "standard" license.

I think * currently * , all Elastic Cloud deployments get assigned with the Enterprise license. However, I'm not sure if this will be the case in the future.

In any case, we'd like Cloud users to be able to use the cloud-smtp connector (which is a preconfigured email connector using Cloud's SMTP infra) and that was the reason for this ask.

@mikecote
Copy link
Contributor Author

In any case, we'd like Cloud users to be able to use the cloud-smtp connector (which is a preconfigured email connector using Cloud's SMTP infra) and that was the reason for this ask.

@Kushmaro, you are good to go on this requirement now :) We have developed preconfigured connectors for this use case. It can be used to pre-configure an email connector on Cloud via kibana.yml configuration.

I think * currently * , all Elastic Cloud deployments get assigned with the Enterprise license. However, I'm not sure if this will be the case in the future.

Keep us posted. With the above, it will be flagged as "usage" of a paid feature and maybe you wouldn't want that?

@gmmorris gmmorris added the estimate:needs-research Estimated as too large and requires research to break down into workable issues label Aug 18, 2021
@gmmorris gmmorris removed the loe:needs-research This issue requires some research before it can be worked on or estimated label Sep 2, 2021
@kobelb kobelb added the needs-team Issues missing a team label label Jan 31, 2022
@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 31, 2022
@mikecote
Copy link
Contributor Author

mikecote commented Jul 8, 2022

Closing for now until we have further requirements (ex: notification center from AppEx core to send emails based on user profile).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
estimate:needs-research Estimated as too large and requires research to break down into workable issues Feature:Actions/Framework Issues related to the Actions Framework Feature:Actions NeededFor:Cloud Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Development

No branches or pull requests

7 participants