|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
_______________________________________________ logback-dev mailing list logback-dev@qos.ch http://mailman.qos.ch/mailman/listinfo/logback-dev
Here is a real world reason: financial markets shut down at 5:15 to 5:45 Eastern USA time every day. (I am not talking about NYSE which is only open during business hours, I'm talking about the ones that are operating most hours per day). Therefore it is best to do any log rotations in that window.
This problem might occur in other settings, where you have a server that is based in, say, the United States, but has a lot of traffic from Asian sources, where Midnight USA may actually a high traffic time for you. This feature would allow you to customize your rollover time to the point that actually is the lowest traffic for your server.
It shouldn't be that hard to implement, I tried to do it myself with a custom class; all you would have to do is replace the hardcoded `0` in `ch.qos.logback.rolling.helper.RollingCalendar` with something parsed from a `timeOfDay` field. I tried to do it myself with a custom class but I ended up with inexplicable `NullPointerException`s and I decided it was easier to simply to the Rolling outside of Logback.