Cricket Users

George Wilbert | 5 Apr 2012 17:30

Monitor Thresholds not working

I have cricket 1.0.5 and for some reason I can only get a single data
source to work with thresholds. And to make it even more weird it's a
different data source on every target.

Any know bugs?? help would be appreciated??

------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second 
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev

headers

Merrett Willett | 9 Apr 2012 14:08

Re: Monitor Thresholds not working

I'm sure there are bugs somewhere, but they work fine if implemented
correctly.  Are you modifying the value collected in the monitor for the
correct data source that is being collected for the target?  Below are
some examples from by Defaults and Targets files.  You should also run a
debug collector to validate the monitors and example (add "-logLevel
debug" to the end of the collector command)

Target examples:

target router01
    target-type=Cisco-Router
    short-desc  =   "router01"
    monitor-thresholds = "%cpu-mem%"

target GigabitEthernet8_0_0
        interface-name      =  GigabitEthernet8/0/0
        short-desc          =  "router01 - G8/0/0"
        monitor-thresholds  =  "%internet%"

Monitor statements from Defaults file:
internet = 
	"ifHCInOctets : value : n : %internet-high% : MAIL : Mail  : %email_list%,
	ifHCOutOctets : value : n : %internet-high% : MAIL : Mail : %email_list%,
	ifInErrors  : quotient : %inerrpct%  : : ifInUcastPackets  : 0 : MAIL :
Mail  : %email_list%,
	ifOutErrors : quotient : %outerrpct% : : ifOutUcastPackets : 0 : MAIL :
Mail  : %email_list%"

    cpu-mem             =
	"cpu1min : value : n : %default-cpu% : MAIL : Mail : %email_list%,

(Continue reading)