I would like to add a new log rotation strategy to fast-logger. My idea is that logs can be rotated each day (00:00:00 - 23:59:59.999). Log files would be named YYYYMMDDTHH:MM:SS-filename.log where the prefix YYYYMMDDTHH:MM:SS indicates the time of the first log message. This log rotation strategy would be orthogonal to the current strategy of rotating by number and size.
Additionally it would to be useful to compress logs after they've been rotated. A simple callback function FilePath -> IO () would allow custom post processing i.e. compression, log-shipping, etc.
If I implement this would you consider pulling it upstream?
I would like to add a new log rotation strategy to
fast-logger
. My idea is that logs can be rotated each day (00:00:00 - 23:59:59.999). Log files would be namedYYYYMMDDTHH:MM:SS-filename.log
where the prefixYYYYMMDDTHH:MM:SS
indicates the time of the first log message. This log rotation strategy would be orthogonal to the current strategy of rotating by number and size.Additionally it would to be useful to compress logs after they've been rotated. A simple callback function
FilePath -> IO ()
would allow custom post processing i.e. compression, log-shipping, etc.If I implement this would you consider pulling it upstream?