-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Comments
Pinging @elastic/kibana-alerting-services (Team:Alerting Services) |
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). |
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. |
@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.
Keep us posted. With the above, it will be flagged as "usage" of a paid feature and maybe you wouldn't want that? |
Closing for now until we have further requirements (ex: notification center from AppEx core to send emails based on user profile). |
The ability for cloud stack monitoring alerts to send emails in basic license.
The text was updated successfully, but these errors were encountered: