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

There's no framework level UI for defining conditions for Action Groups #82412

Closed
gmmorris opened this issue Nov 3, 2020 · 1 comment · Fixed by #83278
Closed

There's no framework level UI for defining conditions for Action Groups #82412

gmmorris opened this issue Nov 3, 2020 · 1 comment · Fixed by #83278
Assignees
Labels
Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@gmmorris
Copy link
Contributor

gmmorris commented Nov 3, 2020

part of #64077

If an Alert Type wants the user to provide conditions for bucketing certain detections into specific Action Groups they ae forced to implement this themselves.

We want a framework level implementation that standardises this ability.

Screenshot 2020-11-03 at 11 08 09

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

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants