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

Alert simulation/preview #49411

Open
mikecote opened this issue Oct 25, 2019 · 6 comments
Open

Alert simulation/preview #49411

mikecote opened this issue Oct 25, 2019 · 6 comments
Labels
estimate:needs-research Estimated as too large and requires research to break down into workable issues Feature:Alerting/RulesFramework Issues related to the Alerting Rules Framework Feature:Alerting/RulesManagement Issues related to the Rules Management UX Feature:Alerting impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. insight Issues related to user insight into platform operations and resilience Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@mikecote
Copy link
Contributor

Ability to preview how an alert / alert type would behave with a given set of parameters. This could be based on historical or mocked data.

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-stack-services (Team:Stack Services)

@mikecote mikecote moved this from Backlog to Long Term in Make it Action Dec 6, 2019
@bmcconaghy bmcconaghy added Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) and removed Team:Stack Services labels Dec 12, 2019
@bvader
Copy link

bvader commented May 14, 2020

Hi Team,
Thanks for considering this feature, it is very important. I am in the field already heavily using the new framework. Alert creation for user is like a mini code / feature / capability development and deployment cycle. So the ease to configure -> test -> observe -> correct cycle is very important especially when configuring the action. Example at a large customer that is integrating with and event management system via the webhook, which parses the alert to then pass on to their notification pipeline. Simulating the alert i.e. not having to deploy the alert, then cause the alert to fire (sometimes not so easy) will speed the up the alerting deployment cycle time and effort, reduce errors / missed alerts and increase the speed to value.

So as an alert creation owner, I want to simulate the alert firing to reduce the time it take for me to deploy a correct and useful alert with minimal time and debug cycle and errors.

@pmuellr
Copy link
Member

pmuellr commented Nov 26, 2020

I created a feature enhancement issue #84417 regarding an "explain" capability for the alerts underlying queries - brief discussion on this noted that this is kind of a baby-step towards alert simulation, so thought I'd reference it here.

@arisonl
Copy link
Contributor

arisonl commented Dec 15, 2020

The ability to run simulation based off of synthetic test data is important in order to test behaviour under conditions and edge cases that are relatively rare and may not be present in the actual historical data.

@mikecote mikecote removed this from 8.x - Candidates in Make it Action Jan 27, 2021
@mikecote mikecote added this to 8.x - Candidates in Kibana Alerting Jan 27, 2021
@gmmorris gmmorris added Feature:Alerting/RulesFramework Issues related to the Alerting Rules Framework Feature:Alerting/RulesManagement Issues related to the Rules Management UX labels Jul 1, 2021
@gmmorris gmmorris added the loe:needs-research This issue requires some research before it can be worked on or estimated label Jul 14, 2021
@gmmorris gmmorris added insight Issues related to user insight into platform operations and resilience estimate:needs-research Estimated as too large and requires research to break down into workable issues labels Aug 13, 2021
@gmmorris gmmorris removed the loe:needs-research This issue requires some research before it can be worked on or estimated label Sep 2, 2021
@gmmorris gmmorris added the impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. label Sep 16, 2021
@mikecote mikecote removed this from Backlog in Kibana Alerting Jan 6, 2022
@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
@XavierM
Copy link
Contributor

XavierM commented Mar 10, 2022

@mikecote and @gmmorris Can you help us to understand the features?

@gmmorris
Copy link
Contributor

@mikecote and @gmmorris Can you help us to understand the features?

TBH this is more of a placeholder, as we don't quite know the feature requirements.
We'd likely want parity with what Watcher provides, but we shouldn't approach this as a copy of Watcher, but rather as an opportunity to find out what our customers might actually want here.

It would be worth chatting with Product.

@XavierM XavierM changed the title Alert simulation Alert ~simulation~ Mar 30, 2022
@XavierM XavierM changed the title Alert ~simulation~ Alert simulation/preview Mar 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
estimate:needs-research Estimated as too large and requires research to break down into workable issues Feature:Alerting/RulesFramework Issues related to the Alerting Rules Framework Feature:Alerting/RulesManagement Issues related to the Rules Management UX Feature:Alerting impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. insight Issues related to user insight into platform operations and resilience Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
No open projects
Development

No branches or pull requests

9 participants