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
I was taking a look at the original implementation and the following question came to my mind: should that really be the responsibility of Amalthea to export it's own logs ?
Checking the k8s logging documentation, I was wondering if this should not be handled by a dedicated sidecar such as fluentd which provides a dedicated output for s3
@sgaist it would be nice if we can pull this off. The problem is that the audit logs are not just a subset of the plain application logs of the operator. But this should be a problem we can solve. I have never heard of fluentd but it seems like what we need.
@sgaist I like your suggestion - I guess the first task would be to improve the logging in general. At the moment the logs are extremely generic and offer no view into how/when the sessions are being created/hibernated/removed.
The implementation of Amalthea V1 provides an option to export logs from the operator to an S3 bucket.
This ticket tracks the port / re-implementation of this feature.
The text was updated successfully, but these errors were encountered: