<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Yes you're right IT does hit the fan then.<br>
<br>
Gary Baluha wrote:
<blockquote
cite="mid:29f517690807221118j3f548510l92cc591b81faa3dc@mail.gmail.com"
type="cite">
<div dir="ltr">I say the color should be brown, then...<br>
<br>
<div class="gmail_quote">On Tue, Jul 22, 2008 at 11:57 AM, Jeff
Newman <<a moz-do-not-send="true"
href="mailto:jeffnewman75@gmail.com">jeffnewman75@gmail.com</a>>
wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Right.
I think the concept is<br>
<br>
Level 1: "warning everyone, something bad could happen, or might not,<br>
may want to look"<br>
- Yellow<br>
Level 2: "Hey look, it was just a warning before, but now, it's bad<br>
and service might<br>
be interrupted unless you take action, this is your last<br>
chance buddy!"<br>
- Red<br>
Level 3: "I've told you repeatedly, and now look whats happened! You've
reached<br>
super critical orange level! That means within minutes<br>
your service will be dead.<br>
run for the hills, the sky is falling, the phone is about<br>
to ring non-stop"<br>
- Orange<br>
<br>
i think 3 levels makes sense for some specific applications.<br>
<font color="#888888"><br>
-jeff<br>
</font>
<div>
<div class="Wj3C7c"><br>
On Mon, Jul 21, 2008 at 4:57 AM, michael nemeth <<a
moz-do-not-send="true" href="mailto:michael.nemeth@lmco.com">michael.nemeth@lmco.com</a>>
wrote:<br>
> Actually the licenses are better example, Right now I can create
numeric<br>
> limits of say<br>
> 97-102 yellow, 103 to 121 red, but have no way of telling when
I go<br>
> over. And that the first quesion<br>
> management going to ask, being they are very happy to see there
money well<br>
> spent with 100%<br>
> utilization.<br>
> My clearcase script DO return rejections. So with orange I could
tell<br>
> management how many times<br>
> (at least that) and how long it was orange . Also, of course try
to handle<br>
> the orange condition!<br>
><br>
> Point is a "Drop Dead, color is useful .<br>
><br>
> Gary Baluha wrote:<br>
><br>
> If that's the case, a fourth color would have the same limitation
;-)<br>
> (That's a lot of disk space if 100% full = gigs of free space)<br>
><br>
> With the lack of a finer granularity, the only option you have is
to create<br>
> a custom script (client-side or server-side should work in this
case) that<br>
> checks the _amount_ (as opposed to _percentage_) of free space,
and set a<br>
> green/yellow/red threshold based on that. You could then set up
the Hobbit<br>
> alert rules like any other test, and it sounds like this would
solve your<br>
> particular problem.<br>
><br>
> (a client-side script would probably be the easiest to set up,
depending on<br>
> how many machines it would need to be propagated to)<br>
><br>
> On Fri, Jul 18, 2008 at 2:57 PM, michael nemeth <<a
moz-do-not-send="true" href="mailto:michael.nemeth@lmco.com">michael.nemeth@lmco.com</a>><br>
> wrote:<br>
>><br>
>> Sorry, disagree!<br>
>> I can have gigs of space left at 100% not critical at all
!!!! Its not<br>
>> "beyond critical" its fatal if you hit zero free !<br>
>> Either one needs finer granularity (isn't numerical limits in
the work)<br>
>> or a new fatal color. I have that run near 100 % all the
time too.<br>
>><br>
>><br>
>> Gary Baluha wrote:<br>
>><br>
>> The philosophy Hobbit uses for alerting is that you're okay
until you<br>
>> reach a certain threshold. At that point (yellow) you still
have to respond<br>
>> to the event and take care of it, before it becomes a bigger
issue. If it<br>
>> continues, then you reach another threshold where stuff can
(and usually<br>
>> does) break. At this point, you _need_ to respond to the
event.<br>
>><br>
>> What you are proposing is a fourth level such that you are
"beyond<br>
>> critical". This is a similar concept to being "fatally
killed" (as opposed<br>
>> to just being "killed"). The trick to running a successful
monitoring<br>
>> system is setting the thresholds in the first place (which is
easier said<br>
>> than done), such that you don't have any false-positives, but
even more<br>
>> importantly, no false-negatives (i.e. an alert you should have
gotten, but<br>
>> didn't).<br>
>><br>
>> Can you give a more specific example (in as far as
I.P./security will<br>
>> allow) of what you are trying to accomplish?<br>
>><br>
>> On Fri, Jul 18, 2008 at 11:52 AM, michael nemeth <<a
moz-do-not-send="true" href="mailto:michael.nemeth@lmco.com">michael.nemeth@lmco.com</a>><br>
>> wrote:<br>
>>><br>
>>> One case I can think of is for even 100% you've lots of
but if you hits<br>
>>> 0 free you HAVE to do<br>
>>> some thing!<br>
>>><br>
>>> Gary Baluha wrote:<br>
>>><br>
>>> On Fri, Jul 18, 2008 at 10:59 AM, Jeff Newman <<a
moz-do-not-send="true" href="mailto:jeffnewman75@gmail.com">jeffnewman75@gmail.com</a>><br>
>>> wrote:<br>
>>>><br>
>>>> Hi,<br>
>>>><br>
>>>> didn't see a reply, so thought i'd do a resend in case
it got lost in<br>
>>>> the shuffle<br>
>>>><br>
>>>> Hi All,<br>
>>>><br>
>>>> Two questions:<br>
>>>><br>
>>>> QUESTION #1: Is it possible to have a third color
alert? Meaning:<br>
>>>><br>
>>>> One of my customers wants a setup like this:<br>
>>>><br>
>>>> Custom script runs on client server, reports:<br>
>>>><br>
>>>> foo : 80<br>
>>>><br>
>>>> for example.<br>
>>>><br>
>>>> They want less than 85 to be green, 85-90 yellow,
90-95 red, and above<br>
>>>> 95 any color, say orange.<br>
>>>> So far as I can tell, I can only use green, yellow,
and red for<br>
>>>> alerts, and blue and purple are reserved.<br>
>>><br>
>>><br>
>>> Currently, no. But it might help to understand why 4
alert levels are<br>
>>> desired.<br>
>>><br>
>>>> QUESTION #2:<br>
>>>><br>
>>>> lets say #1 above is possible, so my script sends
hobbit the status<br>
>>>> line based on the it sees, with the<br>
>>>> status of green, yellow, red, and orange. The hobbit
server recieves<br>
>>>> it, and uses the NCV module to build the rrd etc..<br>
>>>> In hobbit-alerts.cfg to say does the SERVICE keyword
work for custom<br>
>>>> NCV type columns?<br>
>>><br>
>>> The SERVICE tag in hobbit-alerts.cfg works for any column
name, NCV or<br>
>>> otherwise.<br>
>>><br>
>>><br>
>><br>
>><br>
><br>
><br>
><br>
<br>
</div>
</div>
<div>
<div class="Wj3C7c">To unsubscribe from the hobbit list, send an
e-mail to<br>
<a moz-do-not-send="true" href="mailto:hobbit-unsubscribe@hswn.dk">hobbit-unsubscribe@hswn.dk</a><br>
<br>
<br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>