[hobbit] resend: 2 questions

[michael nemeth]

Sorry, disagree!
I can have gigs of space left at 100%  not critical  at all !!!!  Its 
not "beyond critical"  its  fatal if you hit zero free !
Either one needs finer granularity (isn't numerical limits in the work)  
or a new  fatal color.  I have licenses that run near    100 % all the 
time too.


Gary Baluha wrote:
> The philosophy Hobbit uses for alerting is that you're okay until you 
> reach a certain threshold.  At that point (yellow) you still have to 
> respond to the event and take care of it, before it becomes a bigger 
> issue.  If it continues, then you reach another threshold where stuff 
> can (and usually does) break.  At this point, you _need_ to respond to 
> the event.
>
> What you are proposing is a fourth level such that you are "beyond 
> critical".  This is a similar concept to being "fatally killed" (as 
> opposed to just being "killed").  The trick to running a successful 
> monitoring system is setting the thresholds in the first place (which 
> is easier said than done), such that you don't have any 
> false-positives, but even more importantly, no false-negatives (i.e. 
> an alert you should have gotten, but didn't).
>
> Can you give a more specific example (in as far as I.P./security will 
> allow) of what you are trying to accomplish?
>
> On Fri, Jul 18, 2008 at 11:52 AM, michael nemeth 
> <michael.nemeth at lmco.com <mailto:michael.nemeth at lmco.com>> wrote:
>
>     One case I can think of is for even 100% you've  lots of but if
>     you hits 0 free you HAVE to do
>     some thing!
>
>     Gary Baluha wrote:
>>     On Fri, Jul 18, 2008 at 10:59 AM, Jeff Newman
>>     <jeffnewman75 at gmail.com <mailto:jeffnewman75 at gmail.com>> wrote:
>>
>>         Hi,
>>
>>         didn't see a reply, so thought i'd do a resend in case it got
>>         lost in
>>         the shuffle
>>
>>         Hi All,
>>
>>         Two questions:
>>
>>         QUESTION #1: Is it possible to have a third color alert? Meaning:
>>
>>         One of my customers wants a setup like this:
>>
>>         Custom script runs on client server, reports:
>>
>>         foo : 80
>>
>>         for example.
>>
>>         They want less than 85 to be green, 85-90 yellow, 90-95 red,
>>         and above
>>         95 any color, say orange.
>>         So far as I can tell, I can only use green, yellow, and red for
>>         alerts, and blue and purple are reserved.
>>
>>      
>>     Currently, no.  But it might help to understand why 4 alert
>>     levels are desired.
>>
>>         QUESTION #2:
>>
>>         lets say #1 above is possible, so my script sends hobbit the
>>         status
>>         line based on the it sees, with the
>>         status of green, yellow, red, and orange. The hobbit server
>>         recieves
>>         it, and uses the NCV module to build the rrd etc..
>>         In hobbit-alerts.cfg to say does the SERVICE keyword work for
>>         custom
>>         NCV type columns?
>>
>>
>>     The SERVICE tag in hobbit-alerts.cfg works for any column name,
>>     NCV or otherwise.
>>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xymon.com/pipermail/xymon/attachments/20080718/bcd63f29/attachment.html>