Tracking exceptions with Redmine
Staying on top of errors that happen in your production Rails applications is a must. Unfortunately trawling through log files get old really fast, and getting enough information about where the error happened can be hard.
That’s what services like Honeybadger or Airbrake solves. Whenever an error occurs in your application the details are sent to their service, where you are able to see when, where and how many times a given error has occurred.
However, if you’re uneasy about sending this level of details to a third party service – or if you’re simply a cheapskate like me, there is another way using Redmine.
Fortunately that’s very easy. You need two pieces of open source software:
Voila, from your next deployment onwards your Redmine will be receiving bug reports directly from your application, including stack traces, session values, environment variables and all the good stuff you need to investigate the issue.