On Monday, 15 October 2012 13:51:42 UTC-4, Ruby-Forum.com User wrote: > > Hello > > I am having trouble with my rails environment. Everything works fine > excepts that errors in view code does not show a stacktrace, just the > "We're sorry, but something went wrong." page, and the log just shows a > "500 Internal Server Error" line. > > I am running in development mode, and errors in controller code show a > stacktrace. > > Could someone first confirm that rendering view code like: "<% bogus %>" > should indeed show a stacktrace, and not just an "We're sorry, but > something went wrong." page? > > That's all you'll get in production - exposing stack traces to the public is generally considered a potential security hole.
For monitoring errors in production, there are a bunch of choices: - the exception_notification middleware: https://github.com/smartinez87/exception_notification This one has been around forever, and will send you an email every time your users get a 500 Server Error. - Airbrake: airbrake.io Provides a nice web interface and some tools for aggregating error reports, tracking deploys, etc. They've got a free plan if you'd like to try it out. - New Relic: newrelic.com Primarily focused on measuring application performance, but also tracks errors. Also has a free plan to try out. --Matt Jones -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msg/rubyonrails-talk/-/ITj6HcZzl1MJ. For more options, visit https://groups.google.com/groups/opt_out.
