Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:44056
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain prohost.org from 209.85.219.166 cause and error)
Cc: PHP Development <internals@lists.php.net>,
 Davide Mendolia <idaf1er@gmail.com>
Message-ID: <8A9B0E56-82A5-405C-8221-B3B22852AA07@prohost.org>
To: Patrick ALLAERT <patrick.allaert@gmail.com>
In-Reply-To: <cda548cc0905250157k1f9749a2s997e75dad1cea0b5@mail.gmail.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Mon, 25 May 2009 16:38:45 -0400
References: <cda548cc0905250157k1f9749a2s997e75dad1cea0b5@mail.gmail.com>
Subject: Re: [PHP-DEV] APM
From: ilia@prohost.org (Ilia Alshanetsky)

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
>