The problem is…. how does SA know that you knew that it was still down. 

 

Perhaps you are doing maintenance from afar (using vnc or term serv) and reboot the server.  When it comes up you have assumed (which I am sure no one on this list would do) it is fixed and did not get an alert letting you know (because you already got one and you told Dirk to change it so it didn't send you another one). 

 

This is the dilemma and I believe it is better to err on the side of caution. 

 

Putting these entries into maintenance mode would be the best option.  If you know they are still broke quit monitoring them until they are fixed (or at least you think they are).  Once put back into active mode you will get an alert saying it is still down if you were wrong and it still does not work.  If it is up you will not get a down alert and your problem is now solved.  This is how it should work and I am sure that this why there is such a thing as maintenance mode.

 

 

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Riley, Stephen
Sent:
Wednesday, September 03, 2003 2:38 PM
To: '[EMAIL PROTECTED]'
Subject: [5] RE: [SA-list] change in state

 

This is what I asked a couple of weeks ago too.

 

I am siding with Troy. We have people here that rather than put SA in

maintenance will just shut it down and when we find this and start it up we

are alerted regarding all the down conditions that we were already aware of.

 

The checks are set to alert when down and when back up. So we have been

alerted about the down, but upon a restart we are then alerted again.

 

 

 

-----Original Message-----

From: Jason Passow [mailto:[EMAIL PROTECTED]

Sent: Wednesday, September 03, 2003 3:29 PM

To: [EMAIL PROTECTED]

Subject: RE: [SA-list] change in state

 

 

He already got the alert that it was down.  Then started server's alive

again why should he get more down alerts. 

 

(I am just arguing his point not taking sides.)

 

-----Original Message-----

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf

Of Dirk Bulinckx

Sent: Wednesday, September 03, 2003 2:23 PM

To: [EMAIL PROTECTED]

Subject: RE: [SA-list] change in state

 

It is realy down, so were is the problem?

 

 

dirk.

 

 

 

-----Original Message-----

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]

Behalf Of [EMAIL PROTECTED]

Sent: Wed Sep 03 7:41 PM

To: [EMAIL PROTECTED]

Subject: [SA-list] change in state

 

 

Hello,

 

Maybe this has already been asked, and I missed it...

 

 

Currently it appears that SA tracks the current state of a device in RAM

while it's running...  The problem is..  If I have 20-30 devices that are

currently down, and I stop the SA application to make a change, then

re-start it, I now get another 20-30 alerts for devices I already know are

down...  Would tracking device state via a "database/flatfile" be an

option??

 

Thanks,

Troy

 

 

 

 

---

Troy Bruder, Manager - Hosting and Microsoft Services

APT Information Technology Consultants

7540 Windsor Dr. STE 204

Allentown, PA 18195

Phone 610.366.1100 -or- 888.2.GET.APT http://www.aptconsulting.com

 

 

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