Since a longtime we have this idea. We decide however to first go for the remote check option and then maybe still add the master/slave option to.
Dirk Bulinckx. From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Vogl, Tom Sent: Tuesday, January 08, 2008 5:11 PM To: Servers Alive Discussion List Subject: [SA-list] New Feature Idea - Master SA instance Dirk, Here's an idea for your consideration: Master and Slave SA installs. A slave looks like the current SA: GUI, Runs Checks, Can Alert, etc - but includes a new feature: Ability to send current "Check List" and "Status" to a Master SA box. This could be a push "send" after each cycle - or it could simply hold the current status data until polled by the master. (Possible new check - LAST POLLED exceeds X minutes....) The Master SA would most likely be used for Alert configuration only. It would pull in the check list from each machine and the current status and allow for a central alert escalation process. Later down the road, it would be great if the Master could "push" a config to a remote machine - that would mean all checks could be designed and managed from a single location, but run on remote installs of SA. Obviously this would be an Enterprise Feature - probably requiring each "Slave" to be licensed as an enterprise unit. Maybe the Master SA console would be a separate application? Thoughts? -Tom To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected] If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list. To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected] If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list.
