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
A common practice for an operator when reacting to an alert is to check for k8s events kubectl get events -A. Some companies also configure alerting for k8s events using sysdig or dyntrace. Would it make sense for Starboard to record events depending on the scanners, so users can quickly see that an important vuln/configaudit was founs?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
A common practice for an operator when reacting to an alert is to check for k8s events
kubectl get events -A
. Some companies also configure alerting for k8s events using sysdig or dyntrace. Would it make sense for Starboard to record events depending on the scanners, so users can quickly see that an important vuln/configaudit was founs?Beta Was this translation helpful? Give feedback.
All reactions