It would be nice if there was an option to use a log roller function that would spawn a new log after it reaches a specific the size. The logs at some sites can grow quite large and can become difficult to open in a text editor or to transfer for support.

For example once the ppw20171215.log reaches or exceeds 10mb (OL Tech Support size limit) it rolls off the log as ppw20171215_01.log and writes all the new entries to a new document named ppw20171215.log. The ppw20171215.log would always contain the latest entries, but otherwise they would go in order.

ppw20171215_01.log
ppw20171215_02.log
ppw20171215_03.log
ppw20171215_04.log
ppw20171215.log

At the end of the day the ppw20171215.log could be renamed as ppw20171215_05.log to make the history easier

Hi Uomo,

I can't think of many cases where you'd want to split the log files, as it could potentially make searching for information more difficult as you'd have to search into multiple files instead of just one. Then there's the question: "where do we cut-off"? Obviously, we wouldn't want to cut-off login right in the middle of a process, that would make things more confusing.

Also, if your file is higher than 10 mb and you can't email it to Support, they can create a FTP site for you to upload it. And for it to be slow in a text editor, it needs to be much larger than 10 mb, which is actually small for a log file. Trust me, I've seen MUCH bigger log files than this, and never had any real issues opening them in a text editor. In most cases, redoing a search in many different files will end up taking longer than loading a big file.

Regards,
Raphaël Lalonde-Lefebvre