Re: [PEPr] Comment on Networking::Monitor

Hi Justin Patrin, I really not want to troll, you wrote:

On 11 Dec 2004 12:22:51 -0000, bertrand Gugger <bertrand@toggg.com> wrote:

bertrand Gugger (http://pear.php.net/user/toggg) has commented on the proposal for Networking::Monitor. Comment: ** Users dedicaced ** The alert system should be dedicaced to users alerted. Not have whole alerts sent to all users. Check the code, all the alerts are sent to all the users.

That's not functionable.

Alert systems in organizations, web or industry, *must* dispatch to given team. I've been living in some industry with a few factories,

and in each factory a few machines can be computers or PLC on a few nets, with a few human beings around. every alert should go to the right team/person We had to care of the alert system there and it went monstruous.

If some "free" enterprise likes to propose a "free" web watching service and alert, then it *can only* be user dedicaced. Again, with public stuff that monstruous can come quick

As the package organizes the stuff, to do that, the alarm must be run for each combination of users/service and then, a user can get many messages. If I need to build some real alert system, I can never use tis Net_Monitor as it is,

and it's a pity because pear should furnish all around general support.

*What the heck* are you talking about? Please explain this in more plain English, I have no idea what you mean by any of this. "heck" doesn't stand in my dictionary, but I hope that can give more explanation.

(that all is really related to this very ptoposed package Net_Monitor)

** Associated message ** The message associated with the status is a good help, e.g. HTTP 404 can significate a lot of things and it's some more info from the back package to give a message. As the message is stored but won't give a new alert a difference can exist between the server storage and what alert was sent. So 1) the message could depends on the state (1 state <=> 1 message). OR 2) an option could raise alert if only message changes.

It was my understanding that it could *already* be configured to send a message for everey run witht he status of a service *or* send a message only when the service's status changes. Is it my english/american not understandable ?

Anyway php scripts are. Yes, it's only the status making change, so message should not be stored. Anycase only the first message by status's change will be sent. If status remains but message changes thereafter then no more alerts will be sent. Justin, I'm not trolling this time (as never, I was thinking) à+ -- bertrand Gugger (toggg)