Heroku bills by the hour (even on add-ons). Why not turn it on, log your error,
and then disable it?
If the error is on Heroku's side you can then go back to them ask for a logging
refund (not that they have to, but so far they have been very reasonable).
--
Scott Watermasysk
Founder, Kickof
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 herok
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 wro
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. Fo
Hi,
some users are informing me that my application sometimes pop up an
Application Error:
--
Application Error
An error occurred in the application and your page could not be
served. Please try again in a few moments.
If you are the application owner, check your logs for details.
--
I'm
