We're considering moving away from Heroku for this reason. The logging options are horrific, outside of advanced logging. We don't mind paying for value, but logging should be a minimal base feature, available to all. To add fuel to the fire, GetExceptional is now a fee- only service. We love heroku, but it's rapidly moving out of our price range with very basic add ons.
-bt On Jul 20, 9:54 am, Daniele <[email protected]> wrote: > Hi joshmckin, > thank you very much for the support. > I have tried to replicate the problem locally but I have found no > error yet. > I'm thinking a way to save the log realtime so I can parse it > searching for the problem; the "advance" logging addon is out of my > budget. > > On 20 Lug, 15:58, joshmckin <[email protected]> wrote:> I've had a similar > issue, since the application is crashing any system > > built into the application for logging is crashing with it. New relic > > can sometimes catch it but not always. Your best bet is build an > > environment locally similar to Heroku (Nginx/Thin) and see if you can > > replicate the error. For us it turned out Mysql2 gem was throwing > > exceptions that would kill EventMachine and therefore kill Thin. Since > > Thin was giving up its ghost, the logger would not record the > > exception, once we were able to patch Mysql2 we were able to get to > > the root exception. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
