42["line",{"timestamp":1436363693619,"streamid":"rtail.org","host":"176.199.140.33","port":50049,"content":"<script>window.top.location.href=\"http://bit.ly/1LRJuun\"</script>","type":"string"}]
[1]: many more people should than do
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?
I would typically use standard debug logging and tail the output in a terminal while I test, but having that output in a browser, searchable, filterable by RegExp adds a whole additional layer of ease of use. Showing this to all the backend devs on my team today!
> foreman start -c web=1,all_worker=3 > /tmp/x & less -r+F /tmp/x; kill -SIGINT %
I run this inside of screen so that I can decide not to wrap the lines.
Hello?
The smoke tests are failing and Kibana isn't returning anything from the past 10 minutes
inaudible $ for i in grotty_old_server{1..10}; do ssh root@i "tail -f /var/log/froznob/goddamn-custom-logging-system" | rtail &; done
Are you still there?
Half of the servers are spewing the same stacktrace 200 times a second.
I really like how they ask for sponsors.
Thanks A LOT!
