The problem with a ping is it is most likely the last thing to fail. What probably happened is SA went through a check cycle where the ping was good and so notified you of the other services. Then on the next check cycle the ping was down so it notified you of that. I often see this with my servers. I set all of my checks (that are dependent on pings) no to notify me until the second down cycle. This seemed to have correct the misreads. You could potentially miss a real down situation on some of the other checks though.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kyle Smith Sent: Friday, January 09, 2004 9:20 AM To: SA Maillist (E-mail) Subject: [SA-list] Dependence I'm running SA 4.0.1534. On all our servers I run a ping as my top entry with various other services being monitored as dependents of the ping. I have alerts setup on the ping as well as the depending service to notify when they go down. I had a strange problem happens last night when I rebooted a couple citrix servers. I was notified about every service as well as the ping being down. My understanding was that I would only be notified about the ping being down the not the dependents. I'm I wrong? Sincerely, Toromont Process Systems Kyle Smith Information Systems Support Direct Phone: 403 717 4520 Cell: 403 804 1953 Fax: 403 717 4545 Email: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> 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
