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
|