- This topic has 3 replies, 2 voices, and was last updated 6 years, 3 months ago by
.
-
Posts
-
The current solution to the log of events getting too large is to reset it to empty manually. This means that the only way to reduce the size is to also give up recent entries.
I think a better solution would be to provide a user defined size limit on the log page. Once the log reaches the limit, a new entry would delete the oldest entry as well. This method would retain the most recent N entries where N is a user chosen number. An empty value for N would indicate no limit. 10 might be a good initial default.
This is by no means a critical issue but would be appreciated in some future release. Thanks for the consideration.
No, you don’t have to empty the log events: it’s set to the most recent 200 records, and when it’s full it overwrites the oldest record, so it’s on a rotating basis.
Ok, I did not see than anywhere in the documentation. So it already does what I want except with a fixed size much larger than I would want. It still would be nice to have the size be user settable.
- You must be logged in to reply to this topic.