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.
We also have a Vagrant box for each project, and rtail would be trivial to add to the Vagrant template so that every development box has this running on a specific port without any setup or fiddling needed by each developer. At least that's the direction I'm thinking of going in right now, without having actually tried it out. :)
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.