Is there a (sensible) upper limit for log messages?
Posted: Fri Jun 07, 2024 5:40 pm
By default, the duration for storing log messages was set to 7 days (168 hours).
We have a requirement to be able to trace the log further back. Sometimes we need to check which entries a job has caused weeks later.
We have now increased the duration to 2 weeks (336 hours) (Preferences - Application data). However, I have the feeling that it takes much longer to open the log in the browser.
We would like to increase the duration even further, but we are afraid that at some point this will no longer be performant enough.
Are there any guidelines or empirical values as to how long the duration can be set?
Or is it better to activate logging to a CSV file in the "Logging" area? When activating it, I get a message that this function should only be activated when requested by Enfocus support. And the CSV files are apparently only saved for as long as the log database is set.
Thanks for your support,
Peter
We have a requirement to be able to trace the log further back. Sometimes we need to check which entries a job has caused weeks later.
We have now increased the duration to 2 weeks (336 hours) (Preferences - Application data). However, I have the feeling that it takes much longer to open the log in the browser.
We would like to increase the duration even further, but we are afraid that at some point this will no longer be performant enough.
Are there any guidelines or empirical values as to how long the duration can be set?
Or is it better to activate logging to a CSV file in the "Logging" area? When activating it, I get a message that this function should only be activated when requested by Enfocus support. And the CSV files are apparently only saved for as long as the log database is set.
Thanks for your support,
Peter