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
Let's say a batch of logs should be uploaded to the centralized location. It is unsafe to process a file that is currently. It would be great to have a function that will force the use of the next(incremented counter) so that all the logs that were previously created until that moment can be uploaded.
I don't remember what kind of API there exists, but for this use case .rotate() or .forceRotate() that would switch from:
testlog-2017-03-07.13.10.log.1
to
testlog-2017-03-07.13.10.log.2
@ipetrovic11 I've made a change to force a log rotation. The parameter is a boolean that decides if to force the log rotation or not. Default is false. If called without true it will have the normal behaviour.
This is a feature request.
Currently, there is no easy way to force rotation.
The logic for the new rotation can be packed in one nice function and exposed so rotation can happen from the outside.
The text was updated successfully, but these errors were encountered: