Re: [PEPr] Comment on Networking::Monitor

Hi Bertrand G., As I have stated at least once before, it is the responsibility of the end user to decide who gets what kinds of alerts by using Net_Monitor::setAlerts() at whatever stage of the monitoring session he/she chooses. The end user has complete control over which types of alerts get sent to which people by using Net_Monitor::setAlert() and Net_Monitor::setServices. Best, Robert bertrand Gugger 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. ** 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. 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