Airbrake (https://airbrake.io) is a great service to get notified about all of your Rails errors. You'll get an immediate email on exceptions in your app.
An open source project alternative that you'll have to install on your own is Errbit (https://github.com/errbit/errbit)
To debug and get alerted in real time on errors, exception and anything else by email, or other hooks you can use
its free and works great with heroku to catch any errors including local variables, request information, session and cookie, etc
also it seems odd that you reached heroku db limit, since the free tier is 10,000 rows, and if you said nothing is saved I dont think that you really reached that limit
heroku pg:info to see the db info and see the number of the rows
hi elad, thank you. i knew about airbrake, but it's my first with errbit. nice!
will it work on a heroku instance or should i set up it's own virtual server? if it will, i will mark it as the correct, although i was hoping for some kind of a cross site solution from within the code, much like http://railscasts.com/episodes/53-handling-exceptions-revised?view=asciicast and more of this kind.
in conclusion - i guess that for monitoring and logging it's better to hold a secondary, stand-alone server that is always up and monitoring. would love to know if it works properly on heroku to mark as correct
@guyisra, thank you. never heard of this.
will check it out, but just so you know, the problem was undoubtedly the free tier - we've reached max lines, and it wouldn't save any more.
Exactly, you need a server that is always up, so in case of a failure with any of your resources (databases, network or even hardware failures) you'll be notified by the other server. I'd also combine it with a service like Pingdom http://www.pingdom.com/ that will test your site and notify you for broken things/when the app is down.
I'd definitely go with Airbrake since it's better to focus on your app (and pay the $39/m) then on maintenance. This is probably the reason you chose Heroku over AWS.