I just handle it by having NRPE grep through the Nginx error log; that's where you'll see the timeout come in.
Example timeout: 2012/10/22 19:52:10 [error] 2071#0: *7269 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 70.127.166.167, server: www.domain.com, request: "GET /follow_outlink?url=http%3A%2F%2Fblogs.orlandosentinel.com%2Fnews_politics%2F2012%2F10%2Frace-for-hd-49-gets-nastier.html&name=Sentinel%3A%20Race%20for%20HD%2049%20gets%20nastier HTTP/1.1", upstream: "http://unix:/etc/unicorn/domain.sock:/follow_outlink?url=http%3A%2F%2Fblogs.orlandosentinel.com%2Fnews_politics%2F2012%2F10%2Frace-for-hd-49-gets-nastier.html&name=Sentinel%3A%20Race%20for%20HD%2049%20gets%20nastier";, host: "www.domain.com", referrer: "http://www.domain.com/"; On 10/24/12, Aditya Sanghi <[email protected]> wrote: > Hi Guys, > > Thanks for Unicorn, it makes my world rock. You guy have done a wonderful > job and also huge thanks to the predecessors too. > > The default timeout on my Rails app is 30 seconds. The app works fine most > of the time but there are some parts of the app which are slow and > occasionally totter over the 30 sec response time and timeout. Is there a > clean way for me to hook into timeouts and notify myself when timeouts > occur? Something like a chance to email myself or send an airbrake > notification? > > Cheers, > Aditya > _______________________________________________ > Unicorn mailing list - [email protected] > http://rubyforge.org/mailman/listinfo/mongrel-unicorn > Do not quote signatures (like this one) or top post when replying > _______________________________________________ Unicorn mailing list - [email protected] http://rubyforge.org/mailman/listinfo/mongrel-unicorn Do not quote signatures (like this one) or top post when replying
