Closed GoogleCodeExporter closed 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
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
Original comment by acaudw...@gmail.com
on 3 Apr 2014 at 9:05
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
Original issue reported on code.google.com by
jason.h...@gmail.com
on 11 Jun 2013 at 11:08