Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:44058
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain daevel.fr designates 91.121.160.166 as permitted sender)
Message-ID: <4A1B24C9.40606@daevel.fr>
Date: Tue, 26 May 2009 01:07:53 +0200
User-Agent: Mozilla-Thunderbird 2.0.0.19 (X11/20090103)
MIME-Version: 1.0
To: PHP Development <internals@lists.php.net>
References: <cda548cc0905250157k1f9749a2s997e75dad1cea0b5@mail.gmail.com>
In-Reply-To: <cda548cc0905250157k1f9749a2s997e75dad1cea0b5@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] APM
From: php-dev.list@daevel.fr ("Olivier B.")

Hi,

why not use reporting thought syslog ? It's standard and "central 
aggregation" is already available (thought TCP or databases).

Olivier

Patrick ALLAERT a écrit :
> 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
>
>