Yes - I think LogViewPlus has extensive capabilities and if we had the ability to script these capabilities to provide actions as a service that could be very powerful.  I like the idea, but it would take considerable time to implement.  It's not something that we are considering in the medium term.

Taking this a step further, it would be great if LVP could automatically delete log files after X number of days. For example, any log file that hasn't been updated in 10 days would be deleted. I know this would typically be done using a server-side script, but it's a hassle to create scripts, setup CRON jobs, etc... Since we're already using LVP to monitor directories and parse log files, it would be incredibly convenient to have it remove obsolete files as well. I know we can filter old files in the UI, but they continue hanging out on the server, wasting space, etc...

Glad to hear it Brad - third times a charm.   Thanks for the suggestion!

It works now, thanks!

Thanks Brad. We have just released a new BETA version v3.0.27, can you please try again?

This time I was able to recreate the issue.  There was an problem with identification of remote log files.  This could have been impacting other features, so it's a good bug to fix.

Thanks for your help with this one Brad!  Apologies for the back and forth.

I tried Hard Reload, but it's still not removing the deleted files from the Log Files & Filters list. The deleted files are in a subdirectory of the monitored directory, so perhaps it's not checking the directories recursively.

Thanks Brad. We have just released a new BETA version v3.0.26, can you please try again?

I wasn't able to recreate the issue directly, but v3.0.25 had a bug with how files were tracked and I think this was the problem.

I also find Resynchronize / Reload a bit confusing. The reload function is if you close a file because you don't need it and later decide you do. In this case you want to reapply the directory monitor without making any other changes to any of the other files. Importantly, you don't want to remove log entries for a file which has been rolled because the target file no longer contains the log entries you may need.

Alternatively, I could close a file and Reload the monitor to mirror the file system, but only for that specific file. Other files could still show the rolled entries.

Resynchronize is more extreme. Everything gets closed and reopened such that when the operation completes all files will mirror the source files.

I think both commands serve a purpose, but I would like to make the intention more clear. Maybe "Hard Reload" / "Soft Reload" would be better? I have renamed the commands in the latest BETA.



In summary:
Soft Reload = Reopen closed files.
Hard Reload = Close and reopen everything.

I deleted a bunch of files using the LVP file system utility. Then I selected Resynchronize in the directory monitor, but it did absolutely nothing. All the deleted files remain visible in the Files & Filters pane.

As an aside, I find it odd that there's both a Resynchronize option and a Reload option. I realize they perform slightly different functions, but it's confusing to me and would probably be confusing to others as well. For instance, under what circumstance would you want to reload the directory monitor but NOT resynchronize it? I think these should be consolidated into a single function.

Hi Brad,

Just wanted to let you know that we have now released LogViewPlus v3.0.24 as a BETA release.

This release gives you a few more options for closing views.  First, you can now Ctrl+Click on multiple items in the Files & Filters view.  This feature is discussed in another thread, but the idea is that you can now more easily work with groups of files:



We have also added a new "Resynchronize" option to the directory monitor:



The idea behind the Resynchronize command is that we want to mirror the state of the target directory.  So it will do more than just close hanging log files.  It will actually close all log files which have been opened by the directory monitor and then re-apply the directory monitor.  It is similar to executing the "Close All Files" command followed by the "Reload" command, but files will be refreshed where possible - which should preserve filters.

Hope that helps,

Toby

Logs can also be renamed or moved and it would be difficult for LogViewPlus to distinguish these actions from a delete.  Some of these actions may be triggered by other team members without the LVP user's knowledge.  Also, a user may want to continue looking at a log file's contents even if the source data is missing.  One thing we definitely do not want to do is automatically close a view when a user is in the middle of an analysis.

The 'remove deleted' setting does make sense as part of a directory monitor.  However, this is a very old feature and nobody has requested this behaviour before.  That leads me to believe that this is an edge case.  I do not want to complicate the directory monitor configuration without being more confident in the usefulness of this feature.