Thanks for the transfer log Brad.

I have added some additional transfer logging to the latest BETA release of LogViewPlus (v2.5.30). Can you please install this version and...

1. Open any file which has the issue.
2. Open the transfer log.
3. Clear the transfer log (F4).
4. Refresh the file opened in step 1 (F5).  This will hopefully recreate the issue.
5. Send me the log lines now displayed in the transfer log.

If possible, it would be good to execute the above steps after a restart as this would help ensure there is nothing else interfering with the test.

Thanks,

Toby

I sent you one of the transfer logs. If you want to troubleshoot this further, I can execute a series of actions and then send you the log after. But at this point, I can't even keep track of everything we've discussed, so you'd have to send me a specific set of steps and instructions for what you want me to test.

I have taken a closer look at this issue and am still struggling to recreate it.  I will continue investigating, but one thing I have noticed is that there can sometimes be a considerable delay between when the file is refreshed and when the download begins.  I am testing with large files, but the delay is a little strange.  Nothing major - 1 to 3 seconds max.  I am assuming that when you refresh the file never recovers.

There is also a time period where the file is downloaded before parsing begins.  LogViewPlus may seem like it is not busy during this period - especially if the transfer tab is not visible.  From your screenshots, I do not believe this is the case, but I thought it worth mentioning.

It might also be time to take a closer look at the transfer log and, possibly the SFTP server logs.  Does the re-download get triggered successfully?  Are there any signs of a deadlock?  I would be happy to take a look at these logs if you want to send them to me via email.

1. If I close the workspace and reopen it, the file shows up again.
2. After reopening the workspace and selecting the file, clicking the Reload File button makes it disappear again. However, I just noticed, this happens with ALL files. Selecting any file and clicking Reload makes that file disappear from the top pane.
3. I'm not sure what you mean about Directory Monitor vs Workspace. This is a directory monitor configured within a workspace.
4. There are no other files with the same name.
5. There are no errors in the transfer log.

This sounds like the issue we have been trying to recreate.  I have tried several times, but I am unable to reproduce the issue locally.  You seem to be able to recreate the issue pretty consistently, so there must be something I am missing.

If you run the Parser Wizard and save the parser configuration, the log file is refreshed.  As part of the refresh process the file is removed and re-added to the view.  It seems LogViewPlus is getting confused on the refresh.  

After the parser has been configured, are you able to open the file - possibly after a restart?  If you are able to open the file, what happens if you refresh it (F5)?  Are you opening the file directly or through a Directory Monitor or Workspace?  Is there another file with the same name open?  Are there any errors in the SFTP transfer log?

Sorry for all of the questions.  This is a very strange issue.

I updated to the beta. The main window no longer minimizes after saving the formatter. However, the newly added file still disappears from the top pane.

Can you please make sure you are using the latest BETA release?  I believe this issue has been resolved:
https://www.logviewplus.com/download.html

There's a related issue that's happened to me several times now. The first time it happened, I thought it was a fluke, but now it just happened again. Here are the steps to replicate it:

1. Create a new file called debug.log in an SFTP directoy that's already being monitored.
2. The file shows up in both panes.
3. Since the file is a custom JSON format, the dialog automatically opens for you to configure the template.
4. Using the wizard, configure it as custom JSON. Then save the template.

Here's where it gets interesting. When you click the Save button, the dialog closes and the LVP main window minimizes. I don't know why closing a dialog would cause the entire application to minimize, but that's what it does. After I click on the taskbar icon to bring the window back, I notice that  debug.log is no longer shown in the top pane. However, it still appears in the bottom pane.

No idea what's going on here. The file is definitely in the directory and it was displayed in the top pane prior to creating the template.

I agree - indicators and tool-tips are clearly a much better way to handle environment status notifications.  Thanks for pointing this out Brad.  We are planning a release this week, but I will look into making these changes for the following release in a 2 - 3 months.  

You can remove a file from the monitoring list and it will not modify your view (but the target will no longer receive updates).  If you remove a file from your view, it should be removed from the monitoring list as well.  This is why I mentioned that it is file "08-01.log" in your screenshots which clearly shows that something is wrong.  You may have stopped monitoring the other files, but "08-01.log" should be in your view if it is in the monitoring list.  It appears to have been disconnected from the view and I am not sure how this occurred.  I suspect it occurred during a directory monitor or workspace refresh, but it would be good to try to narrow the problem down.

When LogViewPlus monitors files, the goal is not mirroring the file. The goal is to collect all log entries written to the file since monitoring started. If a log file is deleted, from the server monitoring should continue in case the file is recreated (as is often the case with log files).

Understood. The problem is, the top pane doesn't give any indication of whether the file exists and the bottom pane displays a blank filename. This is inconsistent and extremely confusing. Instead, I'd suggest it continue displaying the file name in both panes, but dim and/or italicize the text and show a warning icon next to the file name, When hovering over the icon, it should display a tooltip like "This file no longer exists in the directory". There shoujld also be an option in the context menu to remove the file from the list, which should remove it from both panes.

Likewise, if monitoring times out on a file, instead of removing the file from the list, it should be displayed with a warning icon, to indicate that it's no longer being monitored. When you hover over this icon, it should display a tooltip like "This file is no longer being monitored because it has exceeded the monitoring time limit. To change this limit, navigate to Settings->Application->Tab & Scroll.". You could also provide a context menu option to restart monitoring.