|
So, you want an
additional check box on the alerts "when" that will ignore ALL check errors?
Timeouts, permissions, bad hair days, etc...?
I LIKE IT!
Makes me think, I could
have one alert with only verified downs go to my engineers, and then another
alerts to my catch-all for every thing.
Oooo-ooo!! Even better,
have my Server admins get all the error alerts, and the process engineers get
the verified downs!
Now that would be a nice
feature!
Michael D. Shook
Technical Analyst
Saddle Creek
Corporation
Michael.Shook@saddlecrk.com
863 668
4477 (work)
863 860 4070 (cell)
863 665 1261 (fax)
www.saddlecrk.com
try creating a dependency check to see if you can connect to the
server first before doing a file check.
>>>
[EMAIL PROTECTED] 04/11/06 04:25AM >>>
Which is kind of
my point. I tried to use CheckFiles to test for
certain
conditions,
if CONDITIONS then ALERT
but
what I get is,
if CONDITIONS or ERROR then
ALERT
While this makes sense perhaps for a ping check it isn't that
useful for
testing for the presence of something (rather than testing for
the
absence of a problem), if you see what I mean. With a service check,
you
want an alert if a service is not running, I agree, but with
CheckFiles
I wanted an alert when something IS there, which is
ever-so-slightly
different.
Not anticipating the possible ERROR
results in extra alerts (yep, we use
%e and other parameters in
alerts).
//Steve
-----Original Message-----
From: Dirk Bulinckx
[mailto:[EMAIL PROTECTED]
Sent:
den 11 april 2006 09:55
To: Servers Alive Discussion List
Subject:
[SA-list] RE: [SA-list] False positives
If a check is not OK, then it's
down, that's indeed the way it works.
The
"down" word should be
interpreted as being " no confirmation of it being
UP".
Within the
alert using the %e parameter will show the reason of the
down.
Then you
could see (for example) that an NT service is seen as being
down
because
of "Access Denied" (meaning that at the time of the check we
got
a
access denied back from the OS and as such can't confirm that
the
service is
running).
To unsubscribe send a message with
UNSUBSCRIBE as subject to [email protected]
N.B. The information contained in this electronic message and any attached
documents is privileged, confidential, and protected from disclosure. If you
are not the intended recipient, please note that any review, disclosure,
copying, distribution, or use of the contents of this electronic message or
any attached documents is prohibited. If you received this in error, please
contact the sender and delete the material from any computer.
To unsubscribe send a message with UNSUBSCRIBE as subject to
[email protected] --------------------------------------
The information contained in this message is intended only for the use of the addressee. If the reader of this message is not the intended recipient or agent of the intended recipient, you are hereby notified that any dissemination, distribution, or copying of the message is strictly prohibited.
To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected]
|
