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
Instead of rolling the log files 24hrs after they are created, I was wondering if we could have the option to cause rollover to happen at midnight. This would make it slightly easier to see when an event occurred in the log, i.e. if a client says "It happened on May 28", then I know I only have to look in one log file, instead of potentially 2 files.
I'm not sure if this is an option available to the underlying Android/iOS libraries, so not sure how much effort it would be.
You right! It is a bit annoying
Sadly, CocoaLumberjack comes only with elapsed time windows by default.
So, it is probably possible to achieved this by subclassing DDFileLogger and adding the custom rolling policy, but as you said, it needs a bit of works.
On Android, it seems easier though
Instead of rolling the log files 24hrs after they are created, I was wondering if we could have the option to cause rollover to happen at midnight. This would make it slightly easier to see when an event occurred in the log, i.e. if a client says "It happened on May 28", then I know I only have to look in one log file, instead of potentially 2 files.
I'm not sure if this is an option available to the underlying Android/iOS libraries, so not sure how much effort it would be.
The Python
logging
package has this feature: https://docs.python.org/3/library/logging.handlers.html#timedrotatingfilehandlerCheers
The text was updated successfully, but these errors were encountered: