As far as I know, event recording in PL functions the way log entries are stored in containers that are rotated.
How many *containers* are kept exactly?
What is the exact size of each container and/or how can I know how many entries can be fit in such a container?
I am asking out of curiosity, since I miss any documentation references about it or it's me not reading PL docs diligently enough.
Furthermore, it would be good for me to know what I am translating, and how to document it myself so Polish users can learn what's exactly going on. :)
For what I can see, the log file will be cut and create a new file after 13,744 KB or 13751 KB(rarely to get this size)
And I think the Maximum is 10 *containers* to be keep, or forever? :)
And yes, we should be getting a setting like, keep maximum of 10, 50 *containers* etc. ;)
I've developed an aversion to a boatload of settings, hence the no fine tuning.
At present there are up to 10 archived log files, including the .log itself.
They rotate some time after 4096 512 rows - sometimes going a bit over just because it's convenient (only rotate after end of writing all currently queued events out).
This is indeed not documented :o.
Quote from: BenYeeHua on June 10, 2013, 04:39:57 PM
For what I can see, the log file will be cut and create a new file after 13,744 KB or 13751 KB(rarely to get this size)
And I think the Maximum is 10 *containers* to be keep, or forever? :)
And yes, we should be getting a setting like, keep maximum of 10, 50 *containers* etc. ;)
I have also noticed my container "0" is exactly 13751KB.
Quote from: Support on June 12, 2013, 11:45:09 AM
I've developed an aversion to a boatload of settings, hence the no fine tuning.
At present there are up to 10 archived log files, including the .log itself.
They rotate some time after 4096 rows - sometimes going a bit over just because it's convenient (only rotate after end of writing all currently queued events out).
This is indeed not documented :o.
Thank you for the information and keep refining it. ;)
I'm going to change it to 512 log rows, given the size the log files end up being.
Quote from: Support on June 12, 2013, 12:17:52 PM
I'm going to change it to 512 log rows, given the size the log files end up being.
So, it only read the prolasso.log at the boot right? :)
And how many performance hit(hard disk) for loading log at boot?
As an additional, technical feature: how about adding a button "Event recording info" that would display message box about log entries being recorded and log container rotation (unless you plan to restore the option that allowed to specify rows to be displayed)? It's not a biggie, since advanced users can get to this on their own, but it's always more desirable not to dig in executables using debuggers and/or hex editors (especially when it isn't within the EULA ;D).
Sure, that's something I will add in the next beta series. It would just take a minute, and I'd personally find it desirable information to show.