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
Currently the Cryptnono pod logs are lost when there's an update.
There is a lot of interesting information in the logs, including, which cryptnominers were detected, processes that were incorrectly killed, which repos were involved, etc.
Could we forward the logs to a persistent location? BinderHub already sends some event logs to Google Cloud Logs
Currently the Cryptnono pod logs are lost when there's an update.
There is a lot of interesting information in the logs, including, which cryptnominers were detected, processes that were incorrectly killed, which repos were involved, etc.
Could we forward the logs to a persistent location? BinderHub already sends some event logs to Google Cloud Logs
mybinder.org-deploy/mybinder/values.yaml
Lines 202 to 226 in 69cb5df
so we could do something similar, though there'll be a cost for storing the logs.
Alternatively we could store them somewhere else?
The text was updated successfully, but these errors were encountered: