Better Text Log Handling
It would be helpful if the text logs had a limit to what is displayed and handled so the application does not crash when the text log gets really large. In my case, the log file gets very large very quick (sometimes is as little as a day or two) and occasionally crashed the program. It would be nice to not have to manually clear the logs.
These performance issues have been completely addressed in v2.7.0.7.
Automatic trim of the UI text log file to 1000 records on startup. The log can grow to approx 10,000 lines during operation and then trim in 20% chunks, optimized to display all lines in rich text format. I recommend keeping custom text log files or use the grid log for anything more significant than these numbers.
The grid log will hold up to 20,000 records which load and group in under a second during startup and operation.
Loading of records in the grid and text log are heavily optimized now and does not affect the startup speed of Directory Monitor, processing of large files should really be done outside of Directory Monitor so these limits are set for optimal performance for ‘above normal’ usage.
-
@Anonymous: The ability to timestamp the files (daily and hourly) is already available. You can find this as part of each directories Text Log settings by going to Add/Edit -> Text Log.
The text log handling the idea is referring to is to constrain the visual text log in the user interface. Managing the log files created is much easier since you can create tasks to manage the files created of make use of the timespamping options. The grid and text log in Directory Monitor can get excessive so their needs to be options to manage that.
-
Anonymous commented
Umm it would be good if we could date and time stamp the logs e.g. 20121210_020345_Adam.txt and specify that a new log is to be created hourly, daily etc just until the database is functioning.
-
greg.bendl commented
Werner,
I think being able to limit the log size within the settings would be very helpful. When the application starts to take up over 400 MB of memory, I clear the logs and restart the application. This brings the memory usage down to a little under 50 MB. I would be happy with being able to limit the logs to about 500 to 1000 current records in order to keep memory usage low.
Thank you,
Greg -
Hi Greg,
In the very latest version (2.3.1.1) I have imposed an internal limit on the text log because I had reports of memory usage exploding because it was hanging onto far too much text. This limit is 2MB of text which on average is about 20,000 lines/events. Beyond that limit, 10% of the text log will be trimmed from the top allowing it to grow again without putting too much pressure on the system.
I personally think 20,000 lines is already excessive and impossible to manage from within the application, this is why a separate text log can be generated for post-processing in something more useful like Excel. The Grid Log Plugin also manages this kind of data much better than the Text Log.
If this limit is still too high, would it be beneficial to allow you to set the limit in the text log options? You could then reduce the size to something more manageable like 200 lines and it will chop a percentage off the top each time it reaches the limit. Cutting off just one line is very inefficient and creates some serious processing overhead on busy systems.
Werner