Closed GoogleCodeExporter closed 9 years ago
Ahh. Currently 'logstash-web' provides the actual web interface to view the
data from the websocket.
The websocket:/// output only provides the websocket stream, not any
html/javascript to use it. I admit this is a bit confusing and will try to add
bits to serve the same websocket viewing functionality from both logstash-web
and from the websocket:/// output.
Original comment by jls.semi...@gmail.com
on 6 Jan 2011 at 7:05
Hi,
Thanks for the tip, I did not notice that logstash-web came with a ws viewer
under /ws/index.html .
I ran it and I finally got the logs delivered through the websocket stream.
I found just a small issue with it. It seems to work fine for a while and then
it stops showing any entries in the radiator although logstash keeps sending
events to the websocket (INFO -- logstash: Sending event to websocket.)
If I log something 5 times in a row, it will no longer show anything afterwards
and old entries in the radiator don't really fade out. I use Chrome 8 as a web
browser.
Thanks for your help.
M
Original comment by r4ce2z...@gmail.com
on 7 Jan 2011 at 8:28
Hi,
I would like to let you know that by checking out the latest revision in your
github repository, the problem goes away.
Cheers,
M
Original comment by r4ce2z...@gmail.com
on 7 Jan 2011 at 9:44
Awesome, thanks for testing the master branch!
I have a bunch of more work to do (testing/quality fixes) before pushing a new
version, though if you think today's master branch works well enough I am happy
to cut that as a new gem.
Original comment by jls.semi...@gmail.com
on 7 Jan 2011 at 9:50
Been stable and happy so far, therefore it's a green light from me.
Cheers,
M
Original comment by r4ce2z...@gmail.com
on 7 Jan 2011 at 2:09
Marking fixed.
Original comment by jls.semi...@gmail.com
on 9 Feb 2011 at 2:23
Original issue reported on code.google.com by
r4ce2z...@gmail.com
on 6 Jan 2011 at 2:48