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

Static resolved action group to fire when an alert instance is resolved #82366

Closed
mikecote opened this issue Nov 2, 2020 · 1 comment · Fixed by #82799
Closed

Static resolved action group to fire when an alert instance is resolved #82366

mikecote opened this issue Nov 2, 2020 · 1 comment · Fixed by #82799
Assignees
Labels
enhancement New value added to drive a business result Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@mikecote
Copy link
Contributor

mikecote commented Nov 2, 2020

Part of #49405.

This issue covers the server side portion of the meta issue.

The has been a lot of requests for users wanting to be notified whenever an alert instance is no longer considered "active". The determination of this is done whenever the event log logs a resolved-instance event here.

This issue should add a static action group called resolved that is available to all alert types and allows alert actions to attach themselves to it. This action group should fire using the same logic used to log resolved-instance

@mikecote mikecote added enhancement New value added to drive a business result Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Nov 2, 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
enhancement New value added to drive a business result 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.

4 participants