Thats the concept. Only wake people up if it's really down, nearly dead is visible
only through output or access to the GUI.
You'd probably need an additional line for the user to be able to set the nearly dead
threshold. Anything that returns a value for the rule to interpret would need this.
External coms would need a new variable to return as well. Some checks (port
connector, SQL connection) wouldn't use this at all since they can be only good or bad
by definition, although somthing like the POP3 or URL check might - up is connected
AND returned expected value, nearly dead is connected only, down is neither.
It would also make sense to have this as an option on each check. I can see where
different admins might want to deal with this or not.
Mike
>>> [EMAIL PROTECTED] 01/09/04 11:42AM >>>
With a ping it would be something like
ping <50% -> down
ping <90% -> nearly dead
ping>90% -> up
And what for the other checks?
And the alerts would only fire on a real down?
Dirk.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Michael Shook
Sent: Friday, January 09, 2004 5:23 PM
To: [EMAIL PROTECTED]
Subject: [SA-list] feature request...
I would like to see in the next version a 2nd rule and new status:
The new status would be a "'mostly dead', which we all know is 'partly
alive'" - to quote Miracle Max. This would be tied to a new rule set, the
result of which would ONLY be to set the new status. No alerts, same
schedule, same everything else as the main rule.
The reason is I spend quite a bit of effort providing my team with web
status panels showing when things are less than perfect, but still
functional. This gives my team the ability to fix the squeaky wheel before
it actually falls off. Right now I have 5 levels (using a 5 ping test with a
20% threshold as an example):
1: lamp off (place holder in the status panel for future testing)
2: green - equals SA UP & ping >= 80%
3: blinking green - equals SA UP & ping >= 60%)
4: blinking yellow - equals SA UP & ping >= 40%)
5: blinking red - equals SA DOWN
These intermediate levels have already "saved the day" by preventing a total
collapse of the network via advance warnings from my status panels that
things were worsening.
Because of the great number of different tests and thresholds, the staus
panels involve quite a bit of programming (and adding a test to all of the
different status panels is a right bloody pain!).
In discussion with my team members, only one intermediate level is actually
necessary, so I thought that it would quite tidy if SA was able to provide
this functionality internally. In fact, 95% of the external programming I do
in .asp to support my status panels, would be unecessary if this addition
were made as I could use the html generation to produce the status panels
(especially if the groups would show this status if any of its members had
this status) from SA.
Michael Shook
Technical Support Analyst - Corporate
Saddle Creek Corporation
723 Joe Tamplin Industrial Blvd
Macon GA 31217
478 742 8740 ext. 105 (work)
478 256 9318 (mobile)
478 742 7917 (fax)
[EMAIL PROTECTED]
http://www.saddlecrk.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
