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.

Sign up for GitHub

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

Jump to bottom

[Alerts][License] Define minimum license required for each alert type. #84954

Closed
YulNaumenko opened this issue Dec 3, 2020 · 2 comments · Fixed by #84997
Closed

[Alerts][License] Define minimum license required for each alert type. #84954

YulNaumenko opened this issue Dec 3, 2020 · 2 comments · Fixed by #84997
Assignees
@YulNaumenko
Labels
Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@YulNaumenko
Copy link
Contributor

YulNaumenko commented Dec 3, 2020 •
edited
Loading

  1. Add a minimum license attribute to alert type definition
  2. Define a minimum license requirement in each built in alert type
  3. Each 3rd party alert type should be able to be registered on the basic or another license level.

Part of Meta issue #60767
@YulNaumenko YulNaumenko added Feature:Alerting v8.0.0 release_note:skip Skip the PR/issue when compiling release notes Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) v7.11.0 labels Dec 3, 2020
@elasticmachine
Copy link
Contributor

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

@YulNaumenko YulNaumenko self-assigned this Dec 3, 2020
@YulNaumenko YulNaumenko removed release_note:skip Skip the PR/issue when compiling release notes v7.11.0 v8.0.0 labels Dec 3, 2020
@YulNaumenko YulNaumenko mentioned this issue Dec 4, 2020
Merged
@YulNaumenko YulNaumenko linked a pull request Dec 4, 2020 that will close this issue
[Alerts][License] Define minimum license required for each alert type #84997
Merged
@YulNaumenko YulNaumenko mentioned this issue Dec 8, 2020
Closed
4 tasks
@mikecote
Copy link
Contributor

Closed by #84997.

@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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@YulNaumenko YulNaumenko

Labels
Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[Alerts][License] Define minimum license required for each alert type YulNaumenko/kibana
4 participants
@kobelb @mikecote @elasticmachine @YulNaumenko