tst2005googlecode / logstalgia

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

logstalgia gets out of sync #51

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. I use it in full screen mode, but if I pause it to view some detail, 
unpausing causes it to carry on at 1 sec per sec - ie it never catches up. That 
means pausing for an hour would leave it an hour behind? 
2.
3.

What is the expected output? What do you see instead?

There's no right or wrong on this, maybe a new feature? "--realtime" - so when 
you unpause, it either races or skips to the current time and continues? I 
thought "--sync" would do that - but it doesn't seem to. If I accelerate it 
using the "+" key multiple times, it flies into the future too - which implies 
logstalgia isn't parsing the timestamps?

What version of the product are you using? On what operating system?

Linux, logstalgia-1.03

Please provide any additional information below.

Just an FYI, but I have a filter script that converts our security syslog data 
into NCSA format, so I can view security information in Pong :-) I see firewall 
acl blocks reflecting back packets, email viruses being "ponged", and NIDS 
events slipping through. Brilliant :-)

Now all I need is a 50" monitor on the wall ;-)

Original issue reported on code.google.com by jason.h...@gmail.com on 11 Jun 2013 at 11:08

GoogleCodeExporter commented 9 years ago
Maybe it needs a 'catch up/resync' button.

It is parsing the timestamps but there is nothing currently to stop the 
'simulation time' getting ahead of the log file.

Interesting to hear how you are using it. One of the things on my TODO list is 
to add more support for using it with other logs formats.

Cheers

Andrew

Original comment by acaudw...@gmail.com on 13 Jun 2013 at 1:10

GoogleCodeExporter commented 9 years ago
Yeah - I've seen others ask for more format support, but I think that's a mugs 
game - converting existing data into a format that is supported by logstalgia 
is much more scalable. Perhaps a "contrib" directory of scripts others write 
might be better? Stops you having to add code for starters ;-)

eg I have used logstalgia to show proxy transactions instead of http - easy

tail -F /var/log/squid/access_log | squid2apache | logresolve|logstalgia -

no need for logstalgia to repeat work done by others. Certainly looks 
impressive - the average proxy server is quite a bit busier than the average 
website ;-)

Original comment by jason.h...@gmail.com on 13 Jun 2013 at 2:36

GoogleCodeExporter commented 9 years ago

Original comment by acaudw...@gmail.com on 3 Apr 2014 at 9:05

GoogleCodeExporter commented 9 years ago
I don't see anything committed to git this year about catching up.

I ran with --sync and after 7 hours logstalgia was behind 39 minutes.

Original comment by weedy2...@gmail.com on 2 Sep 2014 at 8:32