You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem?
As an unsure user who is troubleshooting a problem, I want to augment my visualization with anomaly detection, so I can quickly identify if something is problematic or not.
User story: User wants to associate existing anomaly detector to a time series visualization to view anomalies on a dashboard.
Associate existing anomaly detector with a visualization
User wants to create an association between a time series visualization and an existing anomaly detector (which could look at the same data source or another one) in order to overlay the events from the detector on the visualization's timeline.
associate-anomaly-detector.mp4
Screen 1: User selects a visualization on a dashboard and selects "Anomaly detection" from the visualization context menu OuiContextMenu:
Screen 2: User selects "Add anomaly detector" from the context menu:
Screen 3: "Add anomaly detector" option opens a flyout OuiFlyout with "Create anomaly detector" option prefilled with the information from the visualization:
Screen 4: User selects "Associate existing detector" (OuiCheckableCard, OuiRadio):
Screen 5: An alternative path to open "Associate existing detector" flyout is to select Anomaly Detection -> Associated detectors -> Associated detectors flyout -> click on "Associate detector" button. Note on the flyouts behavior - in order to open a new flyout ("Associate detector"), the previous one should be closed ("Associated detectors")
Screen 6: User selects a detector from the list (Single item OuiComboBox):
Screen 7: After selecting a detector user sees a summary of detector's details to review the choice.
Screen 8: After selecting anomaly detector user clicks on "Associate detector" button. The flyout closes, user returns to the dashboard.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?
As an unsure user who is troubleshooting a problem, I want to augment my visualization with anomaly detection, so I can quickly identify if something is problematic or not.
What solution would you like?
opensearch-project/anomaly-detection#521
#400
Meta UX issue
Initial UX proposal on Anomaly Detection on Dashboards opensearch-project/OpenSearch-Dashboards#1798
See also Create anomaly detector from visualizations
User story: User wants to associate existing anomaly detector to a time series visualization to view anomalies on a dashboard.
Associate existing anomaly detector with a visualization
User wants to create an association between a time series visualization and an existing anomaly detector (which could look at the same data source or another one) in order to overlay the events from the detector on the visualization's timeline.
associate-anomaly-detector.mp4
Screen 1: User selects a visualization on a dashboard and selects "Anomaly detection" from the visualization context menu
OuiContextMenu
:Screen 2: User selects "Add anomaly detector" from the context menu:
Screen 3: "Add anomaly detector" option opens a flyout
OuiFlyout
with "Create anomaly detector" option prefilled with the information from the visualization:Screen 4: User selects "Associate existing detector" (
OuiCheckableCard
,OuiRadio
):Screen 5: An alternative path to open "Associate existing detector" flyout is to select Anomaly Detection -> Associated detectors -> Associated detectors flyout -> click on "Associate detector" button.
Note on the flyouts behavior - in order to open a new flyout ("Associate detector"), the previous one should be closed ("Associated detectors")
Screen 6: User selects a detector from the list (Single item
OuiComboBox
):Screen 7: After selecting a detector user sees a summary of detector's details to review the choice.
Screen 8: After selecting anomaly detector user clicks on "Associate detector" button. The flyout closes, user returns to the dashboard.
The text was updated successfully, but these errors were encountered: