-
Notifications
You must be signed in to change notification settings - Fork 0
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
250 frontend alert overview page matching alerts with previous same alerts and display history #279
Conversation
…e' into 250-frontend-alert-overview-page-matching-alerts-with-previous-same-alerts-and-display-history
Signed-off-by: Christoph Klingenberg <[email protected]>
Signed-off-by: Christoph Klingenberg <[email protected]>
Signed-off-by: Christoph Klingenberg <[email protected]>
Signed-off-by: Christoph Klingenberg <[email protected]>
…e' into 250-frontend-alert-overview-page-matching-alerts-with-previous-same-alerts-and-display-history
Signed-off-by: Christoph Klingenberg <[email protected]>
Signed-off-by: Christoph Klingenberg <[email protected]>
…e' into 250-frontend-alert-overview-page-matching-alerts-with-previous-same-alerts-and-display-history
Signed-off-by: Christoph Klingenberg <[email protected]>
Signed-off-by: Christoph Klingenberg <[email protected]>
Signed-off-by: Christoph Klingenberg <[email protected]>
Signed-off-by: Christoph Klingenberg <[email protected]>
Signed-off-by: Christoph Klingenberg <[email protected]>
…rview-page-matching-alerts-with-previous-same-alerts-and-display-history
Signed-off-by: Christoph Klingenberg <[email protected]>
Signed-off-by: Christoph Klingenberg <[email protected]>
Signed-off-by: Christoph Klingenberg <[email protected]>
Signed-off-by: Christoph Klingenberg <[email protected]>
Signed-off-by: Christoph Klingenberg <[email protected]>
Signed-off-by: engelharddirk <[email protected]>
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.
Looks nice so far! I don't see much left to do. I'm not familiar enough with Angular and Clarity to leave you any nit-picks there, though.
" | ||
class="is-solid" | ||
></cds-icon> | ||
{{ summary.mostFrequentAlert.severity }} |
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.
Since the severity alert type inside the History is always the same, the severity also will always be the same. Just throwing the Thought in here, might be sensible to display it anyway.
|
||
<div class="alert-meta" *ngIf="alert.taskId"> | ||
<span> | ||
<strong>Task ID:</strong> {{ alert.taskId }} |
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.
May be easier to follow if we used the task display name. I already informed you about my PR, maybe we can switch that out
…ckend add all remaining requested data from issue
Signed-off-by: Christoph Klingenberg <[email protected]>
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.
Looks very nice, good work!
Signed-off-by: Christoph Klingenberg <[email protected]>
Signed-off-by: Christoph Klingenberg <[email protected]>
…rts-with-previous-same-alerts-and-display-history
history to present same alerts