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
{{ message }}
This repository was archived by the owner on Feb 14, 2022. It is now read-only.
This is the first in a potential series of notification techniques. It is potentially the simplest one, implemented completely in the Clair Dashboard application. Functionality rests on the premise that the application periodically refreshes the samples via the Clair API.
Questions to resolve:
Where to persist a users request to receive notifications? In the browser's local storage? In a cookie?
If the user has access to several installations, for which ones does the Dashboard application emit notifications?
What to do if data are missing? If new data comes in but the time stamp is old, should we still issue a notification?
Which algorithm and which threshold to use to decide on notifications? Ideally, code and the parameters should be shared with the traffic light display in the widget.
When should the notification be reset? Only upon user request? If the browser is closed? after a fixed amount of time?
This is the first in a potential series of notification techniques. It is potentially the simplest one, implemented completely in the Clair Dashboard application. Functionality rests on the premise that the application periodically refreshes the samples via the Clair API.
Questions to resolve:
Complexity: 5
Value: 20
WSJF: 4