maybe it's possible to solve the problem at this way:

The person's scheduler is splitted to full hours for smtp and pager
notification.
Every full hour a routine can query the status of the hosts and 'simulates'
SA a status change when the status is down. 

Michael


> -----Urspr�ngliche Nachricht-----
> Von:  Dirk Bulinckx [SMTP:[EMAIL PROTECTED]]
> Gesendet am:  Donnerstag, 5. September 2002 13:23
> An:   [EMAIL PROTECTED]
> Betreff:      RE: [SA-list] 
> 
> This would mean that for each person we would have to keep a queue for
> each
> entry...don't think we're going to do that.
> 
> Don't forget to vote for Servers Alive in the annual Sunbelt Target Awards
> http://www.sunbelt-software.com/targetawards/
> 
> 
> dirk.
> 
> 
> 
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Jack Lyons (Martin Agency)
> Sent: Thu Sep 05 12:31 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [SA-list]
> 
> 
> can you keep track of the state between don't send times...i.e. at 5pm
> when
> the send option period ends...you have 3 hosts down.   at 6am when the
> send
> option period starts, salive looks at the state at 5pm and compares it to
> the current status, and emails the difference.
> 
> Jack
> ----- Original Message -----
> From: "Dirk Bulinckx" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, September 05, 2002 5:18 AM
> Subject: RE: [SA-list]
> 
> 
> > that would mean going over all entry's and rechecking all people that
> are
> > within the alerts.
> > Also the "don't alert" thing can be different for each person, so when
> > should we check it?
> >
> > Don't forget to vote for Servers Alive in the annual Sunbelt Target
> Awards
> > http://www.sunbelt-software.com/targetawards/
> >
> >
> > dirk.
> >
> >
> >
> > -----Original Message-----
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> > Behalf Of David Walters
> > Sent: Thu Sep 05 11:14 AM
> > To: '[EMAIL PROTECTED]'
> > Subject: RE: [SA-list]
> >
> >
> > why cant you do a speical check when "dont alert" time has finished . im
> not
> > sure how you can do it.. but perhaps a status check?
> >
> > -----Original Message-----
> > From: Dirk Bulinckx [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, 5 September 2002 5:10 PM
> > To: [EMAIL PROTECTED]
> > Subject: RE: [SA-list]
> >
> >
> > If the entry went down during the "don't alert" time it looks like it
> got
> > dropped yes, but basicly SA sends the message to the address/phone you
> > defined and if within that definition you say that it should send during
> > specific hours that's what it does, just doesn't send it.
> > Don't think queing is a solution in this.
> > You could have different aler and different outputs, each showing a
> correct
> > status, you will have to use those too.
> >
> >
> > Don't forget to vote for Servers Alive in the annual Sunbelt Target
> Awards
> > http://www.sunbelt-software.com/targetawards/
> >
> >
> > dirk.
> >
> >
> >
> > -----Original Message-----
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> > Behalf Of Klug, Michael
> > Sent: Thu Sep 05 11:05 AM
> > To: '[EMAIL PROTECTED]'
> > Subject: AW: [SA-list]
> >
> >
> > I see the problem.
> > SA drops the message in the 'don't alert' cycle.
> > What we need is that SA queues the messages and deletes the messages
> when
> > the host comes up in the 'don't alert' cyle from the queue and sends the
> > queued messages at the end of the 'don't alert' cycle.
> >
> >
> > > -----Urspr�ngliche Nachricht-----
> > > Von: Dirk Bulinckx [SMTP:[EMAIL PROTECTED]]
> > > Gesendet am: Donnerstag, 5. September 2002 10:16
> > > An: [EMAIL PROTECTED]
> > > Betreff: RE: [SA-list]
> > >
> > > SA is checking all the time.
> > > If you set SA to alert (paging for example) on status change it will
> try
> > > to
> > > send the page when the status change, however if due to the schedule
> of
> > > the
> > > person that you're sending the page too SA isn't allowed to send the
> page,
> > > the page won't be send.  On a next down situation (next cycle or the
> 50
> > > cycle further when the entry is still down), SA will see that it only
> has
> > > to
> > > send on status change and won't try to send.  SA will first check the
> > > "send
> > > option" (status change, all downs, after 5 downs or whatever you have
> > > set),
> > > if it has to send it will send.  And during the send SA will convert
> the
> > > team/person name(s) to addresses/phonenumbers and at that time it
> could
> be
> > > that due to a persons schedule that it get's no address/phone back and
> > > thus
> > > doesn't send.
> > >
> > >
> > > Don't forget to vote for Servers Alive in the annual Sunbelt Target
> Awards
> > > http://www.sunbelt-software.com/targetawards/
> > >
> > >
> > > dirk.
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> > > Behalf Of David Walters
> > > Sent: Thu Sep 05 10:03 AM
> > > To: '[EMAIL PROTECTED]'
> > > Subject: RE: [SA-list]
> > >
> > >
> > > wouldnt it be better servered for SA to recheck them when the 'dont
> alert'
> > > has finished tho within SA?
> > >
> > > -----Original Message-----
> > > From: Klug, Michael [mailto:[EMAIL PROTECTED]]
> > > Sent: Thursday, 5 September 2002 2:55 PM
> > > To: '[EMAIL PROTECTED]'
> > > Subject: AW: [SA-list]
> > >
> > >
> > > I've the same prob.
> > > I'm using this workaround:
> > > After the non paging cycle i kill the sa-process and open sa again
> using
> a
> > > task scheduler.
> > > It works fine if you have not a lot of non paging cycles for different
> > > hosts. Only your down/up statistics are wrong.
> > >
> > > Michael
> > >
> > > Michael Klug
> > > Lufthansa AirPlus Servicekarten GmbH
> > > Network & Internet Services
> > > Dornhofstr. 36
> > > 63263 Neu-Isenburg
> > > > Phone:  +49 (0) 61 02 204-220
> > > > Fax:      +49 (0) 61 02 204-759
> > > > E-Mail:   [EMAIL PROTECTED]
> > > > Internet: www.airplus.com
> > > >
> > > > -----Urspr�ngliche Nachricht-----
> > > > Von: David Walters [SMTP:[EMAIL PROTECTED]]
> > > > Gesendet am: Donnerstag, 5. September 2002 07:51
> > > > An: '[EMAIL PROTECTED]'
> > > > Betreff: RE: [SA-list]
> > > >
> > > >  'dont alert for these times'
> > > >
> > > > Id like SA to send a message if the service is down once the 'dont
> alert
> > > > for
> > > > these times' has finished
> > > >
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: Dirk Bulinckx [mailto:[EMAIL PROTECTED]]
> > > > Sent: Thursday, 5 September 2002 1:17 PM
> > > > To: [EMAIL PROTECTED]
> > > > Subject: RE: [SA-list]
> > > >
> > > >
> > > > What send option are you using?
> > > >
> > > > You mean that if SA goes down in the non-paging hours, and is still
> down
> > > > during the paging hours that you would like to get a page?  That's
> not
> > > > possible (except if it has to page you on all down cycles)  You
> could
> > > > however using another alert type during these other hours.
> > > >
> > > > Don't forget to vote for Servers Alive in the annual Sunbelt Target
> > > Awards
> > > > http://www.sunbelt-software.com/targetawards/
> > > >
> > > >
> > > > dirk.
> > > >
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> > > > Behalf Of David Walters
> > > > Sent: Thu Sep 05 5:45 AM
> > > > To: '[EMAIL PROTECTED]'
> > > > Subject: [SA-list]
> > > >
> > > >
> > > > Currently I have SA alertin me when the server is down via sms
> between
> > > > certain hours... say 6pm-9pm    now if the server goes down between
> the
> > > > hours of 9pm-7am  I have to remind myself to check.
> > > >
> > > > is there a way to get SA to alert me if still down when the hours
> are
> > > back
> > > > to 7am - 6pm ?
> > > > 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
> > > 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
> > 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

To unsubscribe from a list, send a mail message to [EMAIL PROTECTED]
With the following in the body of the message:
   unsubscribe SAlive

Reply via email to