Being a master would indeed be an enterprise feature..being a slave can be a standard feature however...
Remember it were "thoughts"..... dirk. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Kevin Stone Sent: Mon Jun 02 12:26 AM To: [EMAIL PROTECTED] Subject: RE: [SA-list] A question... That would seem to an "Enterprise" edition only feature... -Kevin > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx > Sent: Sunday, June 01, 2003 5:06 PM > To: [EMAIL PROTECTED] > Subject: RE: [SA-list] A question... > > > That would ofcourse be one of the checks that SA would > internaly do :-) > > > dirk. > > > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Behalf Of Paul Ockenden > Sent: Sun Jun 01 9:25 PM > To: [EMAIL PROTECTED] > Subject: Re: [SA-list] A question... > > > > That's the sort of thing that would be BRILLIANT to have in > SA. If I were you, though, I'd make sure that when running in > 'multiple' mode like, this, the masters and slaves all have > to be properly licenced copies, not the freebie version. That > way it would protect your revenue stream. > > Good luck with the house and office moves!!!! > > P. > > ----- Original Message ----- > From: "Dirk Bulinckx" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Sunday, June 01, 2003 7:40 PM > Subject: RE: [SA-list] A question... > > > > Well you did make me think...and that on a Sunday evening ... > > > > My thoughts: > > " > > SA can operate in 3 modes: > > * normal (as it is now) > > * master > > * slave > > > > on the SA_master you define who are the slaves. For each entry you > > can define who are the entries on the slave(s) that are linked. > > (master_UID_7 has a slave slave_01_UID_45 and slave_02_UID_56) When > > SA_master checks UID_7 it will after the check query sa_slave_01 to > > get the status of uid_45 and it will also query sa_slave_02 > to get the > > status of uid_56. The query will be done via an SSH like > connection > > that will be kept open during the "running" of sa_master > (ofcourse if > > the connection is dropped for whatever reason, we will remake the > > connection). > > > > on the master you define within the alerts that ALL slaves must be > > down > too > > OR "at least y slaves must be down too" and this in > combination with > > the normal alerting rules based on the status on the sa_master. > > > > > > on the add/edit entry screen on sa_master you will be able > to select > > the corresponding slave entries via a list/dropdown/... > (list will be > > read at startup of the master, with an update button on the > GUI -> in > > order no to have too much network traffic). > > > > > > > > on the sa_slave stations you can define what sa_masters are > allowed to > > connect, and the connection will need authentication (like the > > "normal" connection to the ssh server of SA). " > > > > Those are my thoughts on the "issue". > > > > Timeframe for implementation? Unknown :-) Not directly, too busy > > with other things (like moving to a new house and to a new office). > > > > > > > > > > dirk. > > > > > > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > Behalf Of Paul Ockenden > > Sent: Sun Jun 01 7:54 PM > > To: [EMAIL PROTECTED] > > Subject: Re: [SA-list] A question... > > > > > > > Little remark on the "big boy" monitoring systems. > > > * compare the cost > > > * they use agents on the system that are monitored (-> > roll-out is > > > not > > easy > > > by that) > > > * compare the support > > > > Oh, I know, I know. I was simply wondering whether anyone > had set up a > > multiple SA checker system, where part of the checks > involved checking > > the web pages produced by the other SA monitoring points. > Sounds to me > > like it COULD be done - I was just wondering if anyone was actually > > doing it. > > > > P. > > > > > > > > To unsubscribe from a list, send a mail message to > > [EMAIL PROTECTED] With the following in the body of the message: > > unsubscribe SAlive > > > > > > > > To unsubscribe from a list, send a mail message to > > [EMAIL PROTECTED] With the following in the body of the message: > > unsubscribe SAlive > > > > [incoming email checked] > > > > > > To unsubscribe from a list, send a mail message to > [EMAIL PROTECTED] With the following in the body of the message: > unsubscribe SAlive > > > > To unsubscribe from a list, send a mail message to > [EMAIL PROTECTED] With the following in the body of the message: > unsubscribe SAlive > To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive
