unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: "Bráulio Bhavamitra" <braulio@eita.org.br>
Cc: unicorn-public <unicorn-public@bogomips.org>
Subject: Re: Show request details on timeout killing
Date: Fri, 5 Dec 2014 22:16:34 +0000	[thread overview]
Message-ID: <20141205221634.GA4772@dcvr.yhbt.net> (raw)
In-Reply-To: <CAJri6_vPrzo32oyKpE86LT5NkMy8RfMiDhq9xvYgJkr2H4q7hQ@mail.gmail.com>

Bráulio Bhavamitra <braulio@eita.org.br> wrote:
> Rails/nginx already log many request on production.log/access.log, but
> I can't know which of them timeouted.

Can't Rails log when a request starts and finishes?
(I haven't touched Rails in years)

Look for starts on PIDs without finishes.

Something along the lines of the following middlware (totally untested):

    class LogBeforeAfter
      def initialize(app)
        @app = app
      end

      def call(env)
        env["rack.logger"].info("#$$ start #{env['PATH_INFO']}")
        response = @app.call(env)
        env["rack.logger"].info("#$$   end #{env['PATH_INFO']}")
        response
      end
    end

    -------------- config.ru ---------------
    use LogBeforeAfter
    # other middlewares...
    run YourApp.new

See Rack::CommonLogger source for more examples/detail.

      reply	other threads:[~2014-12-05 22:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-04 21:15 Show request details on timeout killing Bráulio Bhavamitra
2014-12-05  1:06 ` Eric Wong
2014-12-05 21:58   ` Bráulio Bhavamitra
2014-12-05 22:16     ` Eric Wong [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://yhbt.net/unicorn/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141205221634.GA4772@dcvr.yhbt.net \
    --to=e@80x24.org \
    --cc=braulio@eita.org.br \
    --cc=unicorn-public@bogomips.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://yhbt.net/unicorn.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).