<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META NAME="Generator" CONTENT="MS Exchange Server version 6.0.6487.1">
<TITLE>Re: [Perfparse-users] Re: [Nagiosplug-devel] Performance output of the disk plugin</TITLE>
</HEAD>
<BODY dir=ltr>
<DIV>I don't know about how to handle the range issue, but I fixed the flipped
values issue. I thought that I posted to this list with the patch, but maybe I
didn't. Check the sourceforge.net nagiosplug site, I posted a patch there
(search for user: g_force). If you can't locate it, let me know and I can dig it
up and resend to the list...</DIV>
<DIV> </DIV>
<DIV>-g</DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV><FONT size=2>-----Original Message----- <BR><B>From:</B>
perfparse-users-admin@lists.sourceforge.net on behalf of Ben Clewett
<BR><B>Sent:</B> Thu 7/22/2004 9:45 AM <BR><B>To:</B> Jaap Hogenberg
<BR><B>Cc:</B> nagiosplug-devel@lists.sourceforge.net;
'perfparse-users@lists.sourceforge.net' <BR><B>Subject:</B> Re:
[Perfparse-users] Re: [Nagiosplug-devel] Performance output of the disk
plugin<BR><BR></FONT></DIV>
<P><FONT SIZE=2>Yes I know the
check_disk returns the values upside down. Very </FONT>
<BR><FONT SIZE=2>annoying! Half my
disks are showing up as CRITICAL too :)</FONT> </P>
<P><FONT SIZE=2>I did post a bug
about this, but not sure what happened to it.</FONT> </P>
<P><FONT SIZE=2>It's early days yet
for performance data, I am sure everything will fall </FONT>
<BR><FONT SIZE=2>into place over next
few months.</FONT> </P>
<P><FONT SIZE=2>I might even find
time to add range support to PerfParse if it's </FONT>
<BR><FONT SIZE=2>important. But
please don't hold your breath!</FONT> </P>
<P><FONT SIZE=2>Regards, Ben</FONT>
</P>
<BR>
<P><FONT SIZE=2>Jaap Hogenberg
wrote:</FONT> </P>
<P><FONT SIZE=2>> On Thu,
2004-07-22 at 16:21, Ben Clewett wrote:</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>>>Jaap,</FONT>
<BR><FONT SIZE=2>>></FONT>
<BR><FONT SIZE=2>>> From the perspective of PerfParse, this
unfortunately does not </FONT>
<BR><FONT SIZE=2>>>understand a range of data. Due to a flaw
in the original data </FONT>
<BR><FONT SIZE=2>>>structure, it can only store a single value each
for the critical and </FONT>
<BR><FONT SIZE=2>>>warn values. Further, it uses these to draw
just single line on the </FONT>
<BR><FONT SIZE=2>>>graphs. Considerable work would be required
to rebuild the product for </FONT>
<BR><FONT SIZE=2>>>a range.</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> OK , I understand.</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>>>You are the
first person I have ever seen who has requested support for </FONT>
<BR><FONT SIZE=2>>>this, and as
far as I know, not a single plugin uses this format :)</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Well, some of my
custom check scripts do ;-)</FONT>
<BR><FONT SIZE=2>> Until I decided to rip that out , because it
confused perfparse :)</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>>>I do note that the range you specify in this case
adds no more </FONT>
<BR><FONT SIZE=2>>>information to the output than using threshold
values.</FONT>
<BR><FONT SIZE=2>>
</FONT>
<BR><FONT SIZE=2>> Uhm,
this particular case is a plugin that reports free space,</FONT>
<BR><FONT SIZE=2>> so the tresholds
are not "upper" treshold but lower tresholds,</FONT>
<BR><FONT SIZE=2>> meaning that when
the value drops BELOW the treshold, a warning or</FONT>
<BR><FONT SIZE=2>> critical status
should be set, with critical < warning</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Just using the
treshold values would generete these alerts when</FONT>
<BR><FONT SIZE=2>> exceeding the
tresholds. </FONT>
<BR><FONT SIZE=2>> That's why I though using ranges would be
usefull.</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Apart from that, the tresholds that this plugin
generates are wrong</FONT>
<BR><FONT SIZE=2>> anyway : it reports the free space, and the
tresholds are not set</FONT>
<BR><FONT SIZE=2>> to 30 and 10 % (in the example below) but to the
values that would be</FONT>
<BR><FONT SIZE=2>> correct when calculating USED space, i.e. 70 and 90
% </FONT>
<BR><FONT SIZE=2>>
</FONT>
<BR><FONT SIZE=2>> All
together, it sounds like we would be better of having a plugin that</FONT>
<BR><FONT SIZE=2>> would report on
used space percentages than free space .....</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Regards, and
thanks for the help</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Jaap Hogenberg</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>>>Somebody here might correct me on this: I
believe the range is used </FONT>
<BR><FONT SIZE=2>>>where an OK range may be either side of a WARN
range, which it's self is </FONT>
<BR><FONT SIZE=2>>>either side of a CRITICAL range. Set by
specifying overlapping ranges:</FONT>
<BR><FONT SIZE=2>>></FONT>
<BR><FONT SIZE=2>>> OK [-WARN--[--CRITIAL--]--WARN-] OK</FONT>
<BR><FONT SIZE=2>>></FONT>
<BR><FONT SIZE=2>>>Or in reverse
where the '@' is used: an OK range sits between a WARN </FONT>
<BR><FONT SIZE=2>>>range, which
sits between a CRITICAL range:</FONT>
<BR><FONT SIZE=2>>></FONT>
<BR><FONT SIZE=2>>>---CRITICAL-]--WARN-] OK
[-WARN--[-CRITIAL---</FONT>
<BR><FONT SIZE=2>>></FONT>
<BR><FONT SIZE=2>>>I do wish to support this one day in PerfParse as
this is a powerful </FONT>
<BR><FONT SIZE=2>>>option. If any person here can shine a
light on how the ranges should </FONT>
<BR><FONT SIZE=2>>>correctly be used, and how to understand
overlapping ranges, and most </FONT>
<BR><FONT SIZE=2>>>important, will standard plugins be written to
use these, and if so, </FONT>
<BR><FONT SIZE=2>>>when? I would be interested in knowing
:)</FONT>
<BR><FONT SIZE=2>>></FONT>
<BR><FONT SIZE=2>>>Regards, Ben.</FONT>
<BR><FONT SIZE=2>>></FONT>
<BR><FONT SIZE=2>>></FONT>
<BR><FONT SIZE=2>>>Jaap Hogenberg
wrote:</FONT>
<BR><FONT SIZE=2>>></FONT>
<BR><FONT SIZE=2>>></FONT>
<BR><FONT SIZE=2>>>>Hi,</FONT>
<BR><FONT SIZE=2>>>></FONT>
<BR><FONT SIZE=2>>>>While playing with perfparse 0.99.01
and the nagios plugin check_disk ,</FONT>
<BR><FONT SIZE=2>>>>it occurs to me that the performance
data for this plugin is not</FONT>
<BR><FONT SIZE=2>>>>correct. When I run the plugin, this is what
I get:</FONT>
<BR><FONT SIZE=2>>>>( currently using check_disk 1.42 from
plugins 1.4.0alpha2 )</FONT>
<BR><FONT SIZE=2>>>></FONT>
<BR><FONT SIZE=2>>>></FONT>
<BR><FONT SIZE=2>>>>nagios@gilmore:~/cvs/nagiosplug/plugins$
./check_disk -w 30% -c 10% -p /</FONT>
<BR><FONT SIZE=2>>>>DISK OK - free space: / 8171 MB (85%);|
/=8170MB;6728;8650;0;9612</FONT>
<BR><FONT SIZE=2>>>></FONT>
<BR><FONT SIZE=2>>>>>From the "plugin developers doc" I gather
that the second and third</FONT>
<BR><FONT SIZE=2>>>>field in the performance data output should
be of the "range type"</FONT>
<BR><FONT SIZE=2>>>>and since we are working with "free space"
any value bigger than </FONT>
<BR><FONT SIZE=2>>>>the warning and critical tresholds is good ,
so we need to alert </FONT>
<BR><FONT SIZE=2>>>>when the value is inside a range using the
"@" sign....</FONT>
<BR><FONT SIZE=2>>>></FONT>
<BR><FONT SIZE=2>>>>This means the "warn" field should
contain @((max * 100)/10:((max *</FONT>
<BR><FONT SIZE=2>>>>100)/30)</FONT>
<BR><FONT SIZE=2>>>>and the
"crit" field should show @[0:]((max * 100) /10</FONT>
<BR><FONT SIZE=2>>>></FONT>
<BR><FONT SIZE=2>>>>in
values: .... | /=8170MB;@961:2884;@0:961;0;9612</FONT>
<BR><FONT SIZE=2>>>></FONT>
<BR><FONT SIZE=2>>>>Is this
right ?</FONT>
<BR><FONT SIZE=2>>>></FONT>
<BR><FONT SIZE=2>>>>I have tried to change the code myself, so
that I could supply </FONT>
<BR><FONT SIZE=2>>>>patches, but my C coding skills are
lousy.</FONT>
<BR><FONT SIZE=2>>>></FONT>
<BR><FONT SIZE=2>>>>I would appriciate the help, and many thanks
for the great work done</FONT>
<BR><FONT SIZE=2>>>>allready!</FONT>
<BR><FONT SIZE=2>>>></FONT>
<BR><FONT SIZE=2>>>>Regards,</FONT>
<BR><FONT SIZE=2>>>>Jaap
Hogenberg</FONT>
<BR><FONT SIZE=2>>>></FONT>
<BR><FONT SIZE=2>>>></FONT>
<BR><FONT SIZE=2>>>></FONT>
<BR><FONT SIZE=2>>>>-------------------------------------------------------</FONT>
<BR><FONT SIZE=2>>>>This
SF.Net email is sponsored by BEA Weblogic Workshop</FONT>
<BR><FONT SIZE=2>>>>FREE Java
Enterprise J2EE developer tools!</FONT>
<BR><FONT SIZE=2>>>>Get your free copy of BEA WebLogic Workshop
8.1 today.</FONT>
<BR><FONT SIZE=2>>>><A HREF="http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click"
>http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click</A></FONT>
<BR><FONT SIZE=2>>>>_______________________________________________</FONT>
<BR><FONT SIZE=2>>>>Nagiosplug-devel mailing list</FONT>
<BR><FONT SIZE=2>>>>Nagiosplug-devel@lists.sourceforge.net</FONT>
<BR><FONT SIZE=2>>>><A href="https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel">https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel</A></FONT>
<BR><FONT SIZE=2>>>>:::
Please include plugins version (-v) and OS when reporting any issue.
</FONT>
<BR><FONT SIZE=2>>>>::: Messages without supporting info will
risk being sent to /dev/null</FONT>
<BR><FONT SIZE=2>>>></FONT>
<BR><FONT SIZE=2>>></FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>>
-------------------------------------------------------</FONT>
<BR><FONT SIZE=2>> This SF.Net email
is sponsored by BEA Weblogic Workshop</FONT>
<BR><FONT SIZE=2>> FREE Java Enterprise J2EE developer
tools!</FONT>
<BR><FONT SIZE=2>>
Get your free copy of BEA WebLogic Workshop 8.1 today.</FONT>
<BR><FONT SIZE=2>> <A HREF="http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click"
>http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click</A></FONT>
<BR><FONT SIZE=2>>
_______________________________________________</FONT>
<BR><FONT SIZE=2>> Perfparse-users
mailing list</FONT>
<BR><FONT SIZE=2>> Perfparse-users@lists.sourceforge.net</FONT>
<BR><FONT SIZE=2>> <A href="https://lists.sourceforge.net/lists/listinfo/perfparse-users">https://lists.sourceforge.net/lists/listinfo/perfparse-users</A></FONT>
<BR><FONT SIZE=2>> </FONT></P>
<BR>
<BR>
<P><FONT SIZE=2>-------------------------------------------------------</FONT>
<BR><FONT SIZE=2>This SF.Net email
is sponsored by BEA Weblogic Workshop</FONT>
<BR><FONT SIZE=2>FREE Java Enterprise J2EE developer tools!</FONT>
<BR><FONT SIZE=2>Get your free copy
of BEA WebLogic Workshop 8.1 today.</FONT>
<BR><FONT SIZE=2><A HREF="http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click"
>http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click</A></FONT>
<BR><FONT SIZE=2>_______________________________________________</FONT>
<BR><FONT SIZE=2>Perfparse-users
mailing list</FONT>
<BR><FONT SIZE=2>Perfparse-users@lists.sourceforge.net</FONT>
<BR><FONT SIZE=2><A href="https://lists.sourceforge.net/lists/listinfo/perfparse-users">https://lists.sourceforge.net/lists/listinfo/perfparse-users</A></FONT>
</P></BLOCKQUOTE>
</BODY>
</HTML>