Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:46442
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.219.226 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type:content-transfer-encoding;
        b=uk7cTvh8FDtBuqzCBCnsZDR3x9s9Jo19L8bLKSpVPsfd1+Hwj6rwbuBVapP6iyaeCh
         QvGjy6rM0dRSGCrvopkSRKkRxVZdOk6IHhujgBdF5WSKbsG0RkesZPE2xdl26xxkljjg
         /LMFf4C0W6+2jBAdxxDwZhYrlN2YmAto6XNSA=
MIME-Version: 1.0
In-Reply-To: <20091216025940.GA19675@joeysmith.com>
References: <3bea96c40912141216u6019bc9bv4bdf054a4cd1919f@mail.gmail.com>
	 <4B275138.4040200@iki.fi> <4B27538C.7030108@daylessday.org>
	 <4B27573D.6080601@iki.fi> <4B2758E6.2070506@daylessday.org>
	 <b9defe2f0912150419s2e701ffdp6a871d1c5e80029c@mail.gmail.com>
	 <4B27802C.9010802@daylessday.org>
	 <bd9320b30912151427p5ca2922fi5d113dd0973ee14d@mail.gmail.com>
	 <20091216025940.GA19675@joeysmith.com>
Date: Tue, 15 Dec 2009 22:29:39 -0500
Message-ID: <68de37340912151929q9f032c0y791e14751e7986d@mail.gmail.com>
To: Joey Smith <joey@joeysmith.com>
Cc: php-dev <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [PATCH] fpm/typo: change some log about dynamic + 
	homogenize log message about pool
From: oorza2k5@gmail.com (Eddie Drapkin)

On Tue, Dec 15, 2009 at 9:59 PM, Joey Smith <joey@joeysmith.com> wrote:
> On Tue, Dec 15, 2009 at 02:27:30PM -0800, Michael Shadle wrote:
>> However if people have ideas on how this will help or be useful (i.e.
>> you -are- planning on running logfiles or logwatch or something) then
>> it might be smart to bring it back to the table again. J=C3=A9r=C3=B4me =
and I
>> were talking about some way to grab statistics in real-time (as close
>> as they can be, obviously the connection counts can change rapidly)
>> and I thought it might make sense to have a PHP function which can
>> access that information. Originally he had mentioned a /url-prefix but
>> that seems a bit complex, having to configure it in the webserver and
>> such.
>
> I don't use FPM, but I certainly am a heavy user of PostgreSQL's 'log_lin=
e_prefix'
> configuration setting. For those who aren't familiar with it, check out t=
he table
> at http://www.postgresql.org/docs/8.4/static/runtime-config-logging.html =
for some
> ideas on the kinds of information you can add (or exclude) from logfile l=
ines. In
> production enviroments, I don't use many of these, as any analysis done o=
n them
> will likely come hours (if not days) after the issue occurred; however, i=
n a
> development or staging environment, knowing something like the PID can be=
 very
> useful. It strikes me that these kind of rules might also apply in the FP=
M case -
> but, again, I'm not actually *using* FPM, so maybe I'm wrong.
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>


I can see this sort of thing being incredibly useful.  I *am* using
FPM in production (dozens of sites, some share pools, some don't) and
if that level of logging was supported, a lot of application-level
logging that I'm doing would be rendered obsolete.  It would be nice
to have a more granular approach to logging what went wrong (knowing
what worker, for instance, which I think is currently unavailable) and
enough information to re-create the problem.  Because of the
operational model of FPM, I think that this idea would greatly improve
the SAPI, especially as part of a development idea.

Definitely a +1 to that idea.