Package forkberjack provides a rolling logger. Note that this is v2.0 of forkberjack, and should be imported using gopkg.in thusly: The package name remains simply forkberjack, and the code resides at https://github.com/natefinch/forkberjack under the v2.0 branch. Forkberjack is intended to be one part of a logging infrastructure. It is not an all-in-one solution, but instead is a pluggable component at the bottom of the logging stack that simply controls the files to which logs are written. Forkberjack plays well with any logging package that can write to an io.Writer, including the standard library's log package. Forkberjack assumes that only one process is writing to the output files. Using the same forkberjack configuration from multiple processes on the same machine will result in improper behavior. To use forkberjack with the standard library's log package, just pass it into the SetOutput function when your application starts.