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

Add "only once" notificiation frequency #81631

Closed
thomasneirynck opened this issue Oct 26, 2020 · 3 comments
Closed

Add "only once" notificiation frequency #81631

thomasneirynck opened this issue Oct 26, 2020 · 3 comments
Labels
Feature:Alerting Project:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@thomasneirynck
Copy link
Contributor

Describe the feature:

Add an "only once" or "at most once" notification option to the alertring framework. When this is selected, only a single notification will be sent as long as the alert is activated.

This would avoid duplicate alerts.

Describe a specific use case for the feature:

This is useful to notify based on "transitions", rather than an evaluation of "current state". When the alert activates, a notification is sent to signal the transition.

This would be particularly useful for the "containment"-option of geo-thresholds. #80749

@YulNaumenko YulNaumenko added Feature:Alerting Project:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Oct 26, 2020
@elasticmachine
Copy link
Contributor

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

@mikecote
Copy link
Contributor

Hi @thomasneirynck, the request sounds similar to Ability to throttle alert instances until state changes #50077? If so, we can close this one as we're tracking the feature under that issue and are planning to work on it in 7.11 🙂

@thomasneirynck
Copy link
Contributor Author

@mikecote yup, sounds the same, thx for flagging!

@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
Labels
Feature:Alerting Project:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Development

No branches or pull requests

5 participants