It's important to know that check the "and when back up too" is different from selecting "when back up after a down".
The "and when back up too" is in combination with another "WHEN" and will only fire IF the "WHEN" that is selected was actualy fired. The "when back up after a down" will send a <mail/page/...> when you get an up after a down, even if no alert was "fired" for that down. dirk. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Kevin Stone Sent: Wed Jun 25 8:22 PM To: [EMAIL PROTECTED] Subject: RE: [SA-list] perfmon cpu utilization check As usual Dirk you're correct. I found a stray alert entry that may be causing my issue, I'll need to test more to be sure. -Kevin > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx > Sent: Wednesday, June 25, 2003 1:43 PM > To: [EMAIL PROTECTED] > Subject: RE: [SA-list] perfmon cpu utilization check > > > That's not correct. The "when back up too" is only trigger > IF the down alert is send too. > > > dirk. > > > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Behalf Of Kevin Stone > Sent: Wed Jun 25 7:28 PM > To: [EMAIL PROTECTED] > Subject: RE: [SA-list] perfmon cpu utilization check > > > Is it a "Down" alert or an "Up" alert? When "and when backup > too" is checked SA will send an up alert every time the > threshold is crossed even if it does not send a down alert > because it hasn't reached the consecutive cycles limit. I > see this a bit with one of our machines. I will get email > saying the CPU is below 90% even though I did not get and > email saying it was above 90%. There isn't any way to get > around this that I know of. > > -Kevin > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > > Behalf Of Gregg Nicholas > > Sent: Wednesday, June 25, 2003 12:50 PM > > To: [EMAIL PROTECTED] > > Subject: RE: [SA-list] perfmon cpu utilization check > > > > > > I tried the suggestions made by Kevin and Dirk. It greatly reduced > > the false reports of problems on the server, but I'm not > sure that the > > counter is being reset correctly. > > > > The test is as follows: > > General: 192.168.7.19, connect via LAN, Keep connection alive > > Check: NT perfmon, Processor,% Processor Time,0, > 99, timeout 30, > > second knock > > Alert: SMTP when 10 times down and then every 10 cycles > > Schedule: every minute > > > > I've gradually increased the number of down events before > the alert is > > supposed to trigger. When I watch the CPU utilization with > taskmgr, > > it is almost always at 0%. It will spike - perhaps every > few minutes > > - but it quickly drops back to 0%. > > > > It's very unlikely that it actually hits 100% on each of 10 > successive > > checks. Nevertheless, I've gotten several alerts today. > Perhaps the > > very act of checking cpu utilization can cause it to hit 100% - > > without lasting long enough to show up on taskmgr? > > > > Is there some better way to do this? > > Is there perhaps a counter that I can check for the average CPU > > utilization over the last 5 minutes? > > > > Thanks, > > Gregg Nicholas > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > > > Behalf Of Kevin > Stone > > > Sent: Tuesday, June 24, 2003 17:12 > > > To: [EMAIL PROTECTED] > > > Subject: RE: [SA-list] perfmon cpu utilization check > > > > > > > > > When you set up the alert you can set it to alert after x > number or > > > checks. Then at the very bottom of the box off to the > right is the > > > checkbox "and when back up too". I do the same thing for > > CPU alerts. > > > > > > -Kevin > > > > 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
