Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:44091
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.161 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type:content-transfer-encoding;
        b=aHUqbHqjGrcvnAYl/YQ8e5mcRuc0TBS6kngkM6yo/caZaTKiptwYBg90mfkBPaXiQ/
         8JCI4Oy1hN/N6AEiEjP8ANVn5PFGqfkU1eaSbb4fNaARlenG+d8Mukd1Sfis+yPTH6gk
         Zkv9zop5Hp0EeM4Eb5QMNOwFWUrSmgfcOO+4Q=
MIME-Version: 1.0
In-Reply-To: <68de37340905251609t76c4ac1fj2b5c7f60761d4c4@mail.gmail.com>
References: <cda548cc0905250157k1f9749a2s997e75dad1cea0b5@mail.gmail.com>
	 <4A1B24C9.40606@daevel.fr>
	 <68de37340905251609t76c4ac1fj2b5c7f60761d4c4@mail.gmail.com>
Date: Fri, 29 May 2009 11:48:44 +0200
Message-ID: <cda548cc0905290248p739b544eob73318ba31aa8d2b@mail.gmail.com>
To: Eddie Drapkin <oorza2k5@gmail.com>
Cc: "Olivier B." <php-dev.list@daevel.fr>, PHP Development <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] APM
From: patrick.allaert@gmail.com (Patrick ALLAERT)

2009/5/26 Eddie Drapkin <oorza2k5@gmail.com>:
> Wheels were made to be reinvented!

I already have wheels but I'd like to have tires, it is much more
comfortable while driving fast :)

> On Mon, May 25, 2009 at 7:07 PM, Olivier B. <php-dev.list@daevel.fr> wrote:
>> Hi,
>>
>> why not use reporting thought syslog ? It's standard and "central
>> aggregation" is already available (thought TCP or databases).

Syslog is really neat, but it doesn't fit our needs. We'd like to have
functionalities mainly focused on advanced error handling and
providing in the future information like: which was the content of
$_POST and what was the PHP stack trace when request at URL u at time
t generated an E_ERROR in script s on line l in a corporate
environment or hosting company hosting hundreds or thousands of PHP
apps with a mix of custom made application and open source ones.

Replacing the callback function at application level isn't manageable
when you don't have the control of the applications, this is why we
started as an extension that could be plugged, transparently, to PHP.

Triggered error could then be forwarded using SNMP, mailing, syslog,
etc. with additional information.

-- 
Patrick Allaert
---
http://code.google.com/p/peclapm/ - Alternative PHP Monitor