Re: [PEPr] Comment on Networking::Monitor
| From: | Justin Patrin | Date: | Sat, 11 Dec 2004 18:20:27 +0000 |
| Subject: | Re: [PEPr] Comment on Networking::Monitor | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-35011@lists.php.net to get a copy of this message | ||
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.
>
> Alert systems in organizations, web or industry, *must* dispatch to given
> team.
>
> If some "free" enterprise likes to propose a "free" web watching service
> and alert, then it *can only* be user dedicaced.
>
> 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.
>
*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.
> ** 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.
>
> Surely it's to be studied with the language interpretation...
>
> Anyway such a package can have a great future !
>
> Proposal information:
> http://pear.php.net/pepr/pepr-proposal-show.php?id=171
>
--
Justin Patrin