Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:30151
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain e-novative.de from 85.214.26.34 cause and error)
Message-ID: <466FD223.3010109@e-novative.de>
Date: Wed, 13 Jun 2007 13:16:51 +0200
Organization: e-novative GmbH
User-Agent: Thunderbird 2.0.0.0 (Windows/20070326)
MIME-Version: 1.0
To: Markus Fischer <markus@fischer.name>
CC: Alexey Zakhlestin <indeyets@gmail.com>,  internals@lists.php.net
References: <466F9623.3050102@fischer.name> <cd5680a20706130103q5c52e23bid428c7c0e5602b@mail.gmail.com> <466FC781.3010601@fischer.name>
In-Reply-To: <466FC781.3010601@fischer.name>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] [PHP4] Logging native PHP function calls
From: stefan.priebsch@e-novative.de (Stefan Priebsch)

Hi Markus,

> The thing is: I need to know specific information of the mysql operations:
> 
> 1) host,user,pass of connects/pconnects (and which type of connect),
> count of connects this very request already had
> 2) sql statement on query, execution time, count of how many statements
> this very request already had

You can configure xdebug to create a trace log showing the parameters
passed to the called functions. This could be a basis for what you need.

> Additional to that I need information like:
> * server ip (multiple servers)
> * remote ip
> * http host (zillions of vhosts)
> * uri
> * user agent string

A quick and maybe dirty idea that comes to my mind is to add a function
call in your application that has these parameter (easy to gather from
$_SERVER etc.) so they show up in the trace logs. Then it's a matter of
processing a gazillion lines of trace log to get out the information you
need, but at least it should be there.

> in the past, profiling things, but I don't see this possible in
> production environment running and getting out the the information I need.

Trace logging in a production environment *absolutely* kills your
performance, so if you have to dedicated test environment, hmmm.

But would you actually create a patched PHP and deploy this in your
production environment. Then I personally would rather opt for running
an xdebug-based trace Sunday morning at 4 am.

Kind regards,

Stefan


-- 
 >e-novative> - We make IT work for you.

 e-novative GmbH - HR: Amtsgericht München HRB 139407
 Sitz: Wolfratshausen - GF: Dipl. Inform. Stefan Priebsch

 http://www.e-novative.de