-
Notifications
You must be signed in to change notification settings - Fork 61
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
Bug fixes for single flow feature #77
Conversation
Signed-off-by: Tyler Ohlsen <ohltyler@amazon.com>
E2E tests failing due to upstream changes in Dashboards which bumped the version in the Will fix in a separate PR to run against the explicit |
get(detector, 'taskState') === DETECTOR_STATE.INIT; | ||
const runningJobsAsString = | ||
isRTJobRunning && isHistoricalJobRunning | ||
? 'detector and historical analysis' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we use sth like "real-time" instead of detector? I think the main contribution of single flow is to let real time and historical analyses share a detector.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right, so the frontend still primarily corresponds starting and stopping a "Detector" with the real-time aspect of it, like how it was before. Single flow basically merged historical detectors into a detector's "Historical analysis". The UI & wording is primarily around this idea now, where you create a detector, and you can either (1) run it (which by default is real-time), and/or (2) run a historical analysis.
This wording was gone through UX and tech writer reviews. Let me know if you still have concerns.
@@ -575,6 +575,7 @@ export const AnomalyHistory = (props: AnomalyHistoryProps) => { | |||
detector={props.detector} | |||
monitor={props.monitor} | |||
isHCDetector={isHCDetector} | |||
isHistorical={props.isHistorical} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you point me the code link to 'The detector was stopped' error message? Cannot find it and thus cannot link between isHistorical and the appearance of 'The detector was stopped'.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just asking, can we fix the issue "AD result chart of historical HC shows detector stopped message" by adding this line?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kaituo the annotations are created in disabledHistoryAnnotations, which is used in AnomalyDetailsChart, which is called in AnomaliesChart, which is called in AnomalyHistory
@ylwu-amzn Yes, see point 2 in description
Signed-off-by: Tyler Ohlsen <ohltyler@amazon.com>
Signed-off-by: Tyler Ohlsen <ohltyler@amazon.com>
Signed-off-by: Tyler Ohlsen ohltyler@amazon.com
Description
This PR fixes 2 bugs found when testing out the single flow feature:
RUNNING
when initially opened, but was changed toFINISHED
soon after).isHistorical
prop to the relevant components, which will hide these annotations if the chart is being rendered in a historical context.Testing:
Screenshots of an example where both realtime and historical jobs were running:
Updated wording in modal:

Updated wording in toast:

Check List
--signoff
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.