pbek/loganalyzer

report view not chronological

uinguzero opened this issue · 5 comments

when running reports on patterns, the results are not in a chronological order.

This is confusing, because some of my patterns need to match each other on the same time, and it is often that they are just scrambled

Example

.+App.Droid
2020-01-09 03:09:01.6183 INFO [3] App.Droid.
found: 1 time(s)
2019-11-22 18:33:38.9810 INFO [3] App.Droid.
found: 1 time(s)
2019-11-26 10:09:54.4780 INFO [3] App.Droid.
found: 1 time(s)
2020-03-13 02:03:42.6300 INFO [3] App.Droid.
found: 1 time(s)

pbek commented

Thank you for your suggestion.

No Problem.

Have to stay, SUPER job you did with this VERY useful tool.
The only thing (besides the issue mentioned above ;)) that i wish for is that i had known this program was out there. Would have made my life a lot easier.

pbek commented

Thank you, pull requests are welcome. 😁

pbek commented

I need more information to reproduce what you are doing. Is there only one log file or more? What's in the log files? What patterns do you use? How does the result look like?

My report for 3 files for example looks like this:

Screenshot_20200421_184503

@uinguzero may means something like that:

2020-12-24_141008

This is a website's log file, written line by line. Even in the absence of timestamp sorting (LogAnalyzer), the log-lines are in timestamp order from older to latest (log file).
The report still mixes the results, like reading parts of the file in different threads and not in serial mode?
Sorry, no time to check the source code. I don't know the "logic" behind the "Report View".
It is not a big deal for me, I use my custom bash and python scripts for this kind of log files.