search

meydrew / otroslogviewer

Automatically exported from code.google.com/p/otroslogviewer
0 stars 0 forks source link

Incorrect internal event filter (?) groups messages #274

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
OtrosViewer does somehow group certain log events, I do not know by what 
measure (nor did I find any docu on that feature on the website).

This leads to the effect that a logfile with eg. 300 entries results in 
something like 20 lines in the view with multiple events in the details. The 
problem is that the time codes are the same for these events but NOT the log 
level nor the message. Why are these messages put together and where can I 
switch this off?!

Pattern Layout used is %d{yyyy-MM-dd HH:mm:ss} %p [%t] %C{1} %F %M %L %m%n and 
I am using the Viewer on Win7 64Bit.

Original issue reported on code.google.com by f.siepm...@gmail.com on 21 Oct 2013 at 3:04

GoogleCodeExporter commented 9 years ago 
I have tracked it down a little more. It appears to me that the problem occurs 
when the message of a log event contains "!" as last character. You can see on 
the screen shots that complete log events are part of the message even though 
they are different loglevel and have different messages. How can this happen?

Original comment by f.siepm...@gmail.com on 22 Oct 2013 at 6:27

Attachments:

GoogleCodeExporter commented 9 years ago 
I further tracked this down. Removing all trailling ! does not help. I guess 
this has something to do with the internal regex filters used by OtrosViewer. 
It seems to be some characters that produce this error, but  I do not now 
which. I will add more screenshots from a log4j file (1.2.15) on a win7 64Bit 
machine. This is a quite severe BUG and I wonder why nobody else has 
experienced it so far. Any help is much appreciated! I really would like to use 
this viewer since the configuration is what I was looking for (auto-markers 
from config) but this bug makes it unusable...

Original comment by f.siepm...@gmail.com on 23 Oct 2013 at 1:50

Attachments:

GoogleCodeExporter commented 9 years ago 
Hello again,
I have found a solution but I would also suggest to check the implementation.

I have switched my timestamp format from yyyy-MM-dd HH:mm:ss to yyyy-MM-dd 
HH:mm:ss,SSS and now everything works alright (PATTERN: %d{yyyy-MM-dd 
HH:mm:ss,SSS} %p [%t] %C{1} %F %M %L %m %n).

BUT I am still convinced that this is a bug. If log events are grouped 
together, as I have explained earlier, it makes only sense when the timestamps 
(%d) are identical AND the message (%m) is identical. And it is important that 
the most severe log level (e.g. ERROR) of the group is shown in the log and not 
in the details. Otherwise people will miss important information/errors.

Original comment by f.siepm...@gmail.com on 25 Oct 2013 at 8:18