From: Jaap H. <jaa...@ma...> - 2004-07-22 15:21:14
|
On Thu, 2004-07-22 at 16:21, Ben Clewett wrote: > Jaap, > > From the perspective of PerfParse, this unfortunately does not > understand a range of data. Due to a flaw in the original data > structure, it can only store a single value each for the critical and > warn values. Further, it uses these to draw just single line on the > graphs. Considerable work would be required to rebuild the product for > a range. OK , I understand. > You are the first person I have ever seen who has requested support for > this, and as far as I know, not a single plugin uses this format :) Well, some of my custom check scripts do ;-) Until I decided to rip that out , because it confused perfparse :) > I do note that the range you specify in this case adds no more > information to the output than using threshold values. Uhm, this particular case is a plugin that reports free space, so the tresholds are not "upper" treshold but lower tresholds, meaning that when the value drops BELOW the treshold, a warning or critical status should be set, with critical < warning Just using the treshold values would generete these alerts when exceeding the tresholds. That's why I though using ranges would be usefull. Apart from that, the tresholds that this plugin generates are wrong anyway : it reports the free space, and the tresholds are not set to 30 and 10 % (in the example below) but to the values that would be correct when calculating USED space, i.e. 70 and 90 % All together, it sounds like we would be better of having a plugin that would report on used space percentages than free space ..... Regards, and thanks for the help Jaap Hogenberg > Somebody here might correct me on this: I believe the range is used > where an OK range may be either side of a WARN range, which it's self is > either side of a CRITICAL range. Set by specifying overlapping ranges: > > OK [-WARN--[--CRITIAL--]--WARN-] OK > > Or in reverse where the '@' is used: an OK range sits between a WARN > range, which sits between a CRITICAL range: > > ---CRITICAL-]--WARN-] OK [-WARN--[-CRITIAL--- > > I do wish to support this one day in PerfParse as this is a powerful > option. If any person here can shine a light on how the ranges should > correctly be used, and how to understand overlapping ranges, and most > important, will standard plugins be written to use these, and if so, > when? I would be interested in knowing :) > > Regards, Ben. > > > Jaap Hogenberg wrote: > > > Hi, > > > > While playing with perfparse 0.99.01 and the nagios plugin check_disk , > > it occurs to me that the performance data for this plugin is not > > correct. When I run the plugin, this is what I get: > > ( currently using check_disk 1.42 from plugins 1.4.0alpha2 ) > > > > > > nagios@gilmore:~/cvs/nagiosplug/plugins$ ./check_disk -w 30% -c 10% -p / > > DISK OK - free space: / 8171 MB (85%);| /=8170MB;6728;8650;0;9612 > > > >>From the "plugin developers doc" I gather that the second and third > > field in the performance data output should be of the "range type" > > and since we are working with "free space" any value bigger than > > the warning and critical tresholds is good , so we need to alert > > when the value is inside a range using the "@" sign.... > > > > This means the "warn" field should contain @((max * 100)/10:((max * > > 100)/30) > > and the "crit" field should show @[0:]((max * 100) /10 > > > > in values: .... | /=8170MB;@961:2884;@0:961;0;9612 > > > > Is this right ? > > > > I have tried to change the code myself, so that I could supply > > patches, but my C coding skills are lousy. > > > > I would appriciate the help, and many thanks for the great work done > > allready! > > > > Regards, > > Jaap Hogenberg > > > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by BEA Weblogic Workshop > > FREE Java Enterprise J2EE developer tools! > > Get your free copy of BEA WebLogic Workshop 8.1 today. > > http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click > > _______________________________________________ > > Nagiosplug-devel mailing list > > Nag...@li... > > https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel > > ::: Please include plugins version (-v) and OS when reporting any issue. > > ::: Messages without supporting info will risk being sent to /dev/null > > > |