← Back to Upcase

Strategy with Heroku and exceptions


(Geoff Harcourt) #1

So all my clients are on Heroku, which is awesome. However, I’m noticing an issue that’s happening a couple times a week, and I’m wondering if forum folks have any ideas.

A couple times a week (across my clients), I get an Airbrake notification of a PG::ConnectionBad error, and the message and backtrace are more or less indicating that there was a temporary loss of connectivity to the AWS instance that hosts the PG database. Do folks exclude these from exception notifications? Is there a good strategy for dealing with these that I’m missing