Just to follow up on my original post: We had one action that we knew
had a timeout problem but we hadn't prioritized fixing it. We
eventually discovered that this action caused other requests to
timeout. The understanding that I got from talking to Heroku support
is when a request comes in it
Aha! Thanks for the explanation. That is very helpful. So, it could
just be a single bad request that pretty much times out all additional
requests down the pipe. We've added rack-timeout already, and next
time we hit one such bad request, we'll know with an exceptional
report!
Subbu.
On
Basically, I update my gemfile with:
gem 'newrelic_rpm'
push, add the new relic addon, and before long, I get a silent crash
of my app. Nothing logged. I've turned it off for the moment
obviously. Is this a known issue? I'm running Rails 3.01 w/ a
mongodb backend.
--
You received this
Ok i'll try that, thanks. Is this on Heroku?
I was under the impression that Heroku overwrites any newrelic.yml
file it finds in the config directory?
On Nov 3, 6:16 am, Dan Croak dcr...@thoughtbot.com wrote:
In our config/newrelic.yml, we have:
disable_mongodb: true
In
