unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Serg Podtynnyi <serg@podtynnyi.com>
To: Eric Wong <normalperson@yhbt.net>
Cc: unicorn list <mongrel-unicorn@rubyforge.org>
Subject: Re: Unicorn logging in production env
Date: Wed, 17 Aug 2011 13:21:39 +0400	[thread overview]
Message-ID: <CAL3dLFqhcTcTc1dyZbL0hzHyg61NE+LX8Vh2Un3-Vzda--gV0Q@mail.gmail.com> (raw)
In-Reply-To: <20110816173034.GA4785@dcvr.yhbt.net>

On Tue, Aug 16, 2011 at 9:30 PM, Eric Wong <normalperson@yhbt.net> wrote:
> Serg Podtynnyi <serg@podtynnyi.com> wrote:
>> Hi All, as I can see on
>> https://github.com/defunkt/unicorn/blob/master/lib/unicorn.rb#L53
>> the Rack::CommonLogger used only in development env and in weird evn
>> called "deployment".
>> Any chance to add  "production" to this case?
>
> Not unless Rack does it, Rack doesn't recognize "production" in any
> special way.
>
> If you really want it, you can add Rack::CommonLogger to config.ru
> yourself.
>
> Since I was never satisfied with the Rack::CommonLogger logging format,
> I wrote clogger[1] which offers nginx-like formatting options.
>
>
>
> [1] http://clogger.rubyforge.org/ - configurable logger for Rack
>
I am asking about this default values because by the convention
production env is 99% "production", but in the code I see
"deployment", so most of the people that are using unicorn have bogus
logs on production. Thanks for clogger suggestion.
PS
Any idea of how to have some kind of useful information when master
process kills workers by timeout?
We just monkey patched Unicorn::HttpParser read method like this
https://gist.github.com/1151164 to get more info. Is there a better
way to do this?
_______________________________________________
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying

  reply	other threads:[~2011-08-17 10:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-16 15:45 Unicorn logging in production env Serg Podtynnyi
2011-08-16 17:30 ` Eric Wong
2011-08-17  9:21   ` Serg Podtynnyi [this message]
2011-08-17  9:58     ` Eric Wong
2011-08-17 10:04       ` Eric Wong
2011-08-16 22:17 ` John Fieber
2011-08-17  0:45   ` Eric Wong

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=CAL3dLFqhcTcTc1dyZbL0hzHyg61NE+LX8Vh2Un3-Vzda--gV0Q@mail.gmail.com \
    --to=serg@podtynnyi.com \
    --cc=mongrel-unicorn@rubyforge.org \
    --cc=normalperson@yhbt.net \
    /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).