-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Comments
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. |
Pinging @elastic/kibana-alerting-services (Team:Alerting Services) |
Yup, this is the question I've been trying to get an answer for. |
Latest mockup for alert details page with the chart:
Notes on the feature from competitive products: https://docs.google.com/presentation/d/15cTbu8xJFm7dKNNCAnBXnBu1Av4GSAyIbQkWQjDmcbQ/edit?usp=sharing |
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). |
Moving from |
2nd part of this Alert Details page Issue:
Adds the Date Range UI and related Chart
1st part: #51546
3rd part: #55424
The text was updated successfully, but these errors were encountered: