Why does it have to be a custom network protocol when using syslog would not only suffice, but also allow for devices that don't run custom code (e.g., switches or routers) to be monitored?
Wow! This is really cool! I would love to use this at my workplace. I had a small problem, though: it seems the clients don't keep very much data.<p>For example, I filtered based on an expression that matched about 1-2 lines per second. The lines appeared, but disappeared almost as quickly. I suspect there is some small client-side buffer that I'm overrunning almost instantly; the log stream I used produces about 500 lines per second. Is this too much for the tool? Can I tune it to work with that load?
Nicely done - the design is amazing. I had to solve a similar problem a while ago and wrote tailon:
<a href="https://github.com/gvalkov/tailon" rel="nofollow">https://github.com/gvalkov/tailon</a>
What is the difference to using websocketd [1] to stream to a socket.io client?<p>[1] <a href="https://github.com/joewalnes/websocketd" rel="nofollow">https://github.com/joewalnes/websocketd</a>