Is your feature request related to a problem? Please describe.
Logs are being printed to stdout only, thus logs are volatile data once the user closes the terminal session. This may lead to operational overhead increase when troubleshooting as logs are not stored anywhere.
Describe the solution you'd like
Log rotation with file writing logs would solve the issue. The logger might require solutions like lumberjack and the usage of io.MultiWriter to enable writer instances write to several output buffers.
In addition, file rotation would preserve a maximum file size for logs, reducing host's disk space consumption (overall log limit required).
Describe alternatives you've considered
None.
Additional context
None.
Is your feature request related to a problem? Please describe.
Logs are being printed to stdout only, thus logs are volatile data once the user closes the terminal session. This may lead to operational overhead increase when troubleshooting as logs are not stored anywhere.
Describe the solution you'd like
Log rotation with file writing logs would solve the issue. The logger might require solutions like
lumberjackand the usage ofio.MultiWriterto enable writer instances write to several output buffers.In addition, file rotation would preserve a maximum file size for logs, reducing host's disk space consumption (overall log limit required).
Describe alternatives you've considered
None.
Additional context
None.