Not updating on every file change and sometimes missing entries when starting session


Not updating on every file change and sometimes missing entries when...
Author
Message
InelLVP
InelLVP
Junior Member (62 reputation)Junior Member (62 reputation)Junior Member (62 reputation)Junior Member (62 reputation)Junior Member (62 reputation)Junior Member (62 reputation)Junior Member (62 reputation)Junior Member (62 reputation)Junior Member (62 reputation)
Group: Forum Members
Posts: 7, Visits: 16
Hello,

We are testing live monitoring of log files and noticed, that LogViewPlus only updates on every second or third file change, so it is effectively behind on showing the current log state (tested with other solutions at the same time and those showed the changes as they happened).
The second issue we noticed is that sometimes entries would go missing when starting session (they would not appear in original view, nor in session view that is supposed to show new changes) and refresh while having session started also yields strange results in many cases.
This was tested with both the latest release and beta versions.
Reply
LogViewPlus Support
LogViewPlus Support
Supreme Being (12K reputation)Supreme Being (12K reputation)Supreme Being (12K reputation)Supreme Being (12K reputation)Supreme Being (12K reputation)Supreme Being (12K reputation)Supreme Being (12K reputation)Supreme Being (12K reputation)Supreme Being (12K reputation)
Group: Moderators
Posts: 1.2K, Visits: 4.3K
Hi Inel,

Thanks for the feedback.

LogViewPlus monitors files by polling them.  A small delay of a fraction of a second is expected.  If you are experiencing delays beyond this it might be a problem with your parser.  In this case, LogViewPlus might be expecting more data in order to complete parsing of the log entry.  Log entries can only be displayed once they have been completely parsed.  

It sounds like you have a significant delay and parsing might be the issue.  I am happy to help with this if you can give me a few sample log entries and the parser configuration you are using.  This might best be done in a separate thread.

Sessions work by taking the last known log entry timestamp and using that as a starting point for a date range filter.  Note that the last known starting point may be several hours ago - or even in a different timezone.  Once the start date is chosen, the filter is simply "show everything after this date".  This is a very simple filter.

Does the session show the correct log entries once started (start date only)?  Does the session show the correct log entries once it is completed (start + end date)?  What happens in both scenarios on a log file refresh?

LogViewPlus does not have the ability to selectively remove or skip a log entry.  So the behavior where it "would not appear in original view" is very strange.  To debug this, I will need more information so I can try to recreate the problem on my side.

Hope that helps,

Toby
GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Threaded View
Threaded View
InelLVP - 5 Years Ago
LogViewPlus Support - 5 Years Ago
InelLVP - 5 Years Ago
LogViewPlus Support - 5 Years Ago
InelLVP - 5 Years Ago
LogViewPlus Support - 5 Years Ago
InelLVP - 5 Years Ago
LogViewPlus Support - 5 Years Ago
InelLVP - 5 Years Ago
LogViewPlus Support - 5 Years Ago
InelLVP - 5 Years Ago
LogViewPlus Support - 5 Years Ago
InelLVP - 5 Years Ago
LogViewPlus Support - 5 Years Ago
LogViewPlus Support - 5 Years Ago

Similar Topics

Login

Explore
Messages
Mentions
Search