Skip to content
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.

historical detector: show readable error message when there is no historical data #361

Closed
ylwu-amzn opened this issue Jan 23, 2021 · 1 comment · Fixed by #364
Closed

historical detector: show readable error message when there is no historical data #361

ylwu-amzn opened this issue Jan 23, 2021 · 1 comment · Fixed by #364

Comments

@ylwu-amzn
Copy link
Contributor

When there is no data in historical detection date range, historical detector task will throw ResourceNotFoundException and write such error message in AD task: There is no data in the detection date range . But we will show Unexpected failure on historical detector detail page. Suggest to show a more readable error message
@ohltyler
Copy link
Contributor

Taking a look. Having discussions on the idea of adding an additional 'No data' state (or something similar) for historical detectors.

@ohltyler ohltyler mentioned this issue Jan 25, 2021
Merged
@ohltyler ohltyler linked a pull request Jan 25, 2021 that will close this issue
Add 'No data' state for historical detectors #364
Merged
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add 'No data' state for historical detectors ohltyler/anomaly-detection-kibana-plugin
2 participants
@ylwu-amzn @ohltyler