Re: APM

Neat idea. Why not open the sqlite db at MINIT rather then RINIT and add a whole pile of overhead to every request. Ilia Alshanetsky On 25-May-09, at 4:57 AM, Patrick ALLAERT wrote:

Hi list, First, I'd like to apologize if the subject of this mail is somewhat off-topic. Davide Mendolia and me are currently working on: "Alternative PHP Monitor" (APM - http://code.google.com/p/peclapm/) which consist of three parts: - a PHP extension which has as a goal of capturing "events" (warning, error, notices,... and slow requests) storing them centrally in an SQLite DB. - a webfrontend to display captured events (for now, it's basically a table without any filtering or querying). - a "central aggregator" which collects events from the different "nodes" (still not developped). I think it is important to mention that we are talking about 100% Free Software here :-) An event is currently characterized with the following properties: - a unique ID - a timestamp - a script filename/line number - an event level corresponding to error levels - a message A "slow request" is characterized with the following properties: - a unique ID - a timestamp - a script filename - a duration We'd like to have your opinion on our "next steps", what is the most important feature according to you: - The development of the central aggregator - Collecting more info related to an "event" (content of variables $GLOBALS, $_GET, $_POST,...) - alert systems (SNMP, Mailing, ...) - Web services - extending the webfrontend Any similarity with existing Israeli products is purely coincidental. :-) Thanks for your help, Patrick --PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php