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

[UI] Alert Details Chart #56280

Open
gmmorris opened this issue Jan 29, 2020 · 6 comments
Open

[UI] Alert Details Chart #56280

gmmorris opened this issue Jan 29, 2020 · 6 comments
Labels
enhancement New value added to drive a business result estimate:medium Medium Estimated Level of Effort Feature:Alerting/RulesManagement Issues related to the Rules Management UX Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@gmmorris
Copy link
Contributor

gmmorris commented Jan 29, 2020

2nd part of this Alert Details page Issue:

Adds the Date Range UI and related Chart

1st part: #51546
3rd part: #55424

@pmuellr
Copy link
Member

pmuellr commented Jan 29, 2020

What do we want to show in this chart? The alert creation chart we currently have is specific to the index threshold alert type, so if this is meant to be similar, will also need to be a per-alert type kinda thing.

The alert creation chart shows a kind of "summary" of the values being checked against the threshold(s). It shows a sense of how the values change over time, but does not show exact points when an alert would be "triggered".

For alert details, we may want that same chart data - let's call it "historical summary", and also show the actual points when the alert was actually triggered, which we would presumably get from the event log.

@Bargs Bargs added the Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) label Jan 29, 2020
@elasticmachine
Copy link
Contributor

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

@gmmorris
Copy link
Contributor Author

What do we want to show in this chart? The alert creation chart we currently have is specific to the index threshold alert type, so if this is meant to be similar, will also need to be a per-alert type kinda thing.

The alert creation chart shows a kind of "summary" of the values being checked against the threshold(s). It shows a sense of how the values change over time, but does not show exact points when an alert would be "triggered".

For alert details, we may want that same chart data - let's call it "historical summary", and also show the actual points when the alert was actually triggered, which we would presumably get from the event log.

Yup, this is the question I've been trying to get an answer for.
ATM this is an unknown, which is why I've separated it into a new issue.

@arisonl
Copy link
Contributor

arisonl commented Jun 24, 2020

Latest mockup for alert details page with the chart:

alertdetail

  • The histogram shows the monitored metric at any given point in time when the alerting condition is evaluated, for the time window which is selected through the time picker.
  • The chart should show the threshold(s) as line(s) and the points in time when the thresholds are breached.
  • How do we visualise the multiple instances? Do we create multiple charts, one per instance, or combine in one?
  • Is this the alert details page for all types of alerts? In that case, a histogram is not necessarily applicable to all types of alerts? E.g. TLS expiration.
  • Is a histogram the right choice if you have a large window selected with the time picker? In that case you might have a more continuous picture (dense data points).

Notes on the feature from competitive products: https://docs.google.com/presentation/d/15cTbu8xJFm7dKNNCAnBXnBu1Av4GSAyIbQkWQjDmcbQ/edit?usp=sharing

@gmmorris
Copy link
Contributor Author

gmmorris commented Jul 2, 2020

Looking at that chart it occurs to me that perhaps this should be provided not by the framework, but by the solution that implements the AlertType, as only they would know what kind of visualisation would make sense.

We can built the one for IndexThreshold, and the Alerts Details page would know how to inject the ReactComponent that is provided by the Alert Type (like we already do in the flyout for an AlertType's custom fields).

@mikecote mikecote added the enhancement New value added to drive a business result label Sep 3, 2020
@mikecote
Copy link
Contributor

mikecote commented Feb 4, 2021

Moving from 7.x - Candidates to 8.x - Candidates (Backlog) after the latest 7.x planning session.

@gmmorris gmmorris added the Feature:Alerting/RulesManagement Issues related to the Rules Management UX label Jul 1, 2021
@gmmorris gmmorris added loe:needs-research This issue requires some research before it can be worked on or estimated loe:large Large Level of Effort labels Jul 14, 2021
@gmmorris gmmorris removed the loe:needs-research This issue requires some research before it can be worked on or estimated label Jul 14, 2021
@gmmorris gmmorris added the estimate:medium Medium Estimated Level of Effort label Aug 18, 2021
@gmmorris gmmorris removed the loe:large Large Level of Effort label Sep 2, 2021
@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
enhancement New value added to drive a business result estimate:medium Medium Estimated Level of Effort Feature:Alerting/RulesManagement Issues related to the Rules Management UX Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
No open projects
Development

No branches or pull requests

7 participants