If the servers are very busy I would increase the timeout to 10 seconds and enable second knock. 4 seconds is pretty short for a busy device. You could also set it not to alert you until it had been down for 2-3 cycles depending on your requirements.
-Kevin > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Navarrete, Jose > Sent: Thursday, March 06, 2003 5:36 PM > To: Salive (E-mail) > Subject: [SA-list] Monitoring NT service: w3svc > > > Hello, > I am having problems monitoring the W3SVC service in three > very busy IIS servers. Several times the Alert generates DOWN > messages even thou the Server is running fine. I had > increased the timeout value to 4 seconds to prevent the > "false" alerts but I am not sure if it is a good value > (maybe it is too > high) to have a true reading for the W3SVC service. > > Any help is appreciated, > Jose. > > > 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
