At theScore (where I work currently), we use Airbrake for our error reporting. An error happens, the error gets sent to Airbrake and then we're notified via email. We can then investigate all the goodness from their website. Fantastic!
Most ruby apps are centered around some kind of web-service (mainly Ruby on Rails). As such, Airbrake has really good Rails integration – even on their rake tasks! Airbrake is in a lot of our projects, some of which that do not use Rails, however.
A problem that I noticed while debugging why a rake task hadn't reported errors to Airbrake was two fold:
Isn't that crazy? Here's the (insane) code that necessitates it. It definitely wasn't at the forefront of my mind to realize that enabling
rescue_rake_exceptions wouldn't rescue from… rake exceptions.
The solution is to follow their wiki entry (which I had to edit to make it correct):
require 'airbrake/rake_handler' # require this if you don't have rails loaded Airbrake.configure do |config| config.rescue_rake_exceptions = true end
I've raised the issue on Airbrake's github. Feel free to visit the link and weigh in!
Update: a solution that forces the user to deal with this oversight has been created (by me!).
Update 2: success! The pull request has been merged into the project.