Re: [PATCH] fpm/typo: change some log about dynamic + homogenize log message about pool
| From: | Michael Shadle | Date: | Tue, 15 Dec 2009 22:27:30 +0000 |
| Subject: | Re: [PATCH] fpm/typo: change some log about dynamic + homogenize log message about pool | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-46435@lists.php.net to get a copy of this message | ||
On Tue, Dec 15, 2009 at 4:25 AM, Antony Dovgal <tony@daylessday.org> wrote:
> Here we have time, pid, function and line.
> With log_level=debug all of them are printed, in other cases only time gets into the log,
> which makes perfect sense to me.
+1 to Antony and Jérôme.
Having a log format parameter seems a bit overkill for debug/internal messages.
Unless php-fpm's logfile turns into some kind of access log that winds
up being parsed, I don't see the need.
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érôme 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'm thinking of something like APC's apc_cache_info() - returns a
structured array of useful info. Then you could build anything you
wish around it (although you would have to execute it through the
FPM-enabled SAPI most likely)