Hi,

Thanks for reaching out.  "Clear all log entries ..." is the correct application setting.  I think you are having a problem with your parser configuration rather than the new setting.

The dialog you are seeing is LogViewPlus's attempt to understand a new log format.  This should not be needed if the format is already known.  I see the file pattern is "*.log".  This pattern is usually reserved for the Basic Parser which requires no configuration.  Can you check your parser configurations and confirm that the configured patterns are setup correctly?  I would expect 'client.log' to point to a known pattern.  It may help to create the initial setting based on static log file.

If you want to send me the log file name and a sample log entry, I may be able to help with creating a valid configuration pattern.

Hope that helps,

Toby

Hello,

I work for a medium-sized developer and I'm currently investigating the feasibility of us using LogViewPlus to view and debug the logs generated by the software we make. It has lots of killer features that would be very useful for us, but unfortunately at least one killer drawback.

The software being developed generates a text log, and overwrites this log each time the application is started. By default, LogViewPlus keeps the output from old logs in its view, so if you run the application five times and then try to filter the view, you see output from the previous four runs along with the current run. This confuses the output and is not desired.

I found the option in LogViewPlus settings to "Clear all log entries when the log file is rolled or recreated" which looks like it should solve this. However, when this option is enabled, LogViewPlus now shows the following prompt when the software being developed is restarted.



LogViewPlus then has to be restarted, or the logfile has to be re-added to its view, in order to view logs again.

A potential factor is that the log-generating software, when restarted, copies the old log file and renames it within the same folder. For example, if the application is set to write logs to client.log, when it starts up it will copy the previous client.log to client-backup-<timestamp>.log and then start a new client.log file. This behaviour may or may not be related.

Has anyone seen this issue before, and/or know how to fix it?