perfparse-users — Problems using PerfParse

Re: [Perfparse-users] Old Data isn't deleted..

[Ben C. <Be...@cl...>]

Hi Philipp,

I am sorry to hear that your data was not deleted.  Can I ask if the=20
deletion process completed successfully?  If not, or an error was=20
detected, the MySQL probably rolled back the transaction and un-deleted=20
your data.  It's trying to be helpful :)

Can I suggest that you try to delete a host's data, see if it works,=20
then try two host's data, then four...  Try and see where the problem=20
lies.  After all the legacy data is gone, a single nightly deletion=20
should work well.

Regards, Ben.

Sand Philipp wrote:
> Hello list,
>=20
> I got a little prob with my database maintenace. My perdata_service_bin=
 table is about 5gigs large, so I wanted to delete all the data older the=
n 14 days.
> I got to the web gui, and configured the templates to delete all older =
then 14 days. Then I ran perfdata-db-purge. It took about 1 day...
> After that day I did a simple select on the table to show all the data =
older then 14 days and...*wooosch*...the hole stuff was still there??!! (=
took about an hour to take this query :) )
> Is there a prob with the dbpurger script?
> I used the perfparse version 0.100.01 and the 0.101.01.
>=20
> Regards,
> Philipp
>=20
> _____________________________
>=20
> Philipp Sand
> OC-CC-TEC-SYS
>=20
> SYCOR GmbH
> Heinrich-von-Stephan-Stra=DFe 1-5
> D - 37073 G=F6ttingen
>=20
> Telefon	+49 (0) 551 / 490 - 0
> Telefax	+49 (0) 551 / 490 - 232468
>=20
> phi...@sy...
> www.sycor.de
> ------------------------------------------------
>=20
>=20
>=20
> ************************************************
>=20
> sycor plastics - die neue Branchenl=F6sung f=FCr die Kunststoffindustri=
e
>=20
> www.sycor-plastics.de
>=20
> ************************************************
>=20
>=20
>=20
>=20
> Diese E-Mail ist vertraulich und kann dar=FCber hinaus pers=F6nliche In=
formationen beinhalten. Wenn Sie nicht der bestimmungsgem=E4=DFe Empf=E4n=
ger sind, l=F6schen Sie bitte die E-Mail und deren Anh=E4nge sofort und b=
enachrichtigen Sie uns dar=FCber. Die Firma sycor willigt in keine Vertr=E4=
ge oder vertragliche Verpflichtungen ein oder =FCbermittelt rechtsverbind=
liche Angebote, die in Form von E-Mail versandt werden, sofern dies nicht=
 ausdr=FCcklich in schriftlicher Form zwischen den Parteien vereinbart wu=
rde.
>=20
> This e-mail is confidential and may contain personal and/or privileged =
information. If you are not the intended recipient please delete this e-m=
ail and all attachments immediately and inform us. The company sycor does=
 not agree with contracts or contract obligations sent by e-mail, neither=
 do we transmit legally binding offers by e-mail, unless this is not expr=
essly agreed upon between the parties and documented in written form.
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJourna=
l
> Use IT products in your business? Tell us what you think of them. Give =
us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out =
more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> Perfparse-users mailing list
> Per...@li...
> https://lists.sourceforge.net/lists/listinfo/perfparse-users
>=20

[Perfparse-users] Old Data isn't deleted..

[Sand P. <Phi...@sy...>]

Hello list,

I got a little prob with my database maintenace. My perdata_service_bin t=
able is about 5gigs large, so I wanted to delete all the data older then =
14 days.
I got to the web gui, and configured the templates to delete all older th=
en 14 days. Then I ran perfdata-db-purge. It took about 1 day...
After that day I did a simple select on the table to show all the data ol=
der then 14 days and...*wooosch*...the hole stuff was still there??!! (to=
ok about an hour to take this query :) )
Is there a prob with the dbpurger script?
I used the perfparse version 0.100.01 and the 0.101.01.

Regards,
Philipp

_____________________________

Philipp Sand
OC-CC-TEC-SYS

SYCOR GmbH
Heinrich-von-Stephan-Stra=DFe 1-5
D - 37073 G=F6ttingen

Telefon	+49 (0) 551 / 490 - 0
Telefax	+49 (0) 551 / 490 - 232468

phi...@sy...
www.sycor.de
------------------------------------------------



************************************************

sycor plastics - die neue Branchenl=F6sung f=FCr die Kunststoffindustrie

www.sycor-plastics.de

************************************************




Diese E-Mail ist vertraulich und kann dar=FCber hinaus pers=F6nliche Info=
rmationen beinhalten. Wenn Sie nicht der bestimmungsgem=E4=DFe Empf=E4nge=
r sind, l=F6schen Sie bitte die E-Mail und deren Anh=E4nge sofort und ben=
achrichtigen Sie uns dar=FCber. Die Firma sycor willigt in keine Vertr=E4=
ge oder vertragliche Verpflichtungen ein oder =FCbermittelt rechtsverbind=
liche Angebote, die in Form von E-Mail versandt werden, sofern dies nicht=
 ausdr=FCcklich in schriftlicher Form zwischen den Parteien vereinbart wu=
rde.

This e-mail is confidential and may contain personal and/or privileged in=
formation. If you are not the intended recipient please delete this e-mai=
l and all attachments immediately and inform us. The company sycor does n=
ot agree with contracts or contract obligations sent by e-mail, neither d=
o we transmit legally binding offers by e-mail, unless this is not expres=
sly agreed upon between the parties and documented in written form.

[Perfparse-users] New version 0.101.1

[Ben C. <be...@cl...>]

Dear friends,

It's my pleasure to release a new version, 0.101.1.

http://prdownloads.sourceforge.net/perfparse/perfparse-0.101.1.tar.gz?download

The main parser has been recoded by our friend Yves into a modular unit 
which can be endlessly extended and accept data in many different ways.

Don't worry if you like it as-is, there is still a perfparse.sh and if 
you like running from the command line, where as you used to use 
'perfparse -r', it's now 'perfparse-log2db -r -s'.

For those people who don't like killing Nagios on every run, this offers 
a solution to this problem.  In fact two solutions.

Please have a look at the UPGRADE document, and read the other documents 
re-written by Yves in the docs directory.

Finally I have to note that this is of course a mayor rewrite.  If you 
are the first to spot an error, please let us know so that you are the 
last to spot it as well :)

More to come over the next few versions, including *instant* Nagios -> 
Perfparse storage.  As well as an exciting MySQL -> PerfParse optional 
connections instead of PerfParse -> MySQL as we have now.

If anybody want to have a go, an RRD export module is now very simple. 
Please look as the storage code 'storage-print' files.  Simply copy and 
edit for any storage method you desire...

Please enjoy our new version,

Regards, Ben Clewett.

Re: [Perfparse-users] How to handle multiple performance files.

[Yves M. <yme...@li...>]

> I'm using PerfParse 0.100.6 to read these files.  The problem being
> experienced at the moment is; although the filenames are unique, PP use=
s
> the state of the previously processed file when parsing the next file.

[...]

> Ideally, PP would retain the state for each unique filename that has
> been processed.

Have a try on perfparse-0.101.0ym22 : I worked on having a different file=
 to store the
read position for each parsed file. If you scan serviceperf.log, the file=
 that contain
the read position will be called something like perfparse_log.serviceperf=
.log.mark (I
found nothing better :)

I still have problems with my provider, so instead of using
http://ymettier.chez.tiscali.fr/perfparse-devel/, please use
http://ymettier.free.fr/perfparse-devel/

Yves



--=20
- Homepage    - http://ymettier.free.fr - http://www.logicacmg.com -
- GPG key     - http://ymettier.free.fr/gpg.txt                    -
- Maitretarot - http://www.nongnu.org/maitretarot/                 -
- Perfparse   - http://perfparse.sf.net/                           -

Re: [Perfparse-users] How to handle multiple performance files.

[Yves M. <yme...@li...>]

> This results in errors while processing.  The errors relate to file
> length changes and hash values not matching.  In the table,
> perfdata_state, there is only one filename with state information.  It
> appears each file processed overwrites the record of the previously
> processed file.
>
> Ideally, PP would retain the state for each unique filename that has
> been processed.

This is a feature of 0.101. In fact, you get a filename that you can rena=
me yourself if
you want.
Please tell us what pattern you would like for such a file name and I'll =
see how I can
implement it.


> What is the best way of configuring PP to handle this situation?  What
> is the concept behind domains in PP?  Is there a better way of doing
> what I'm trying to achieve?

I suggest that you try perfparse-0.101.0ym21 that is maybe the last pre-v=
ersion before
0.101.1.
Well, I have a problem with my provider. I usually put my files there :
http://ymettier.chez.tiscali.fr/perfparse-devel/perfparse-0_101_0/index.p=
hp
But you will find 0.101.0ym21 here : http://ymettier.free.fr/perfparse-de=
vel/

Don't try 0.101.0ym20 : the feature you are asking is bugged in 0.101.0ym=
20 and solved
in 0.101.0ym21.

Yves


--=20
- Homepage    - http://ymettier.free.fr - http://www.logicacmg.com -
- GPG key     - http://ymettier.free.fr/gpg.txt                    -
- Maitretarot - http://www.nongnu.org/maitretarot/                 -
- GTKtalog    - http://www.nongnu.org/gtktalog/                    -

[Perfparse-users] Tip for installing PP 0.100.7 on Fedora Core 2

[Nick P G S. <ni...@sm...>]

I am new to Nagios and Perfparse, but though this might be useful to someone:

I was having trouble installing PP on RH FC 2, although I had all the
prerequisite packages installed, I was getting lots of compile errors like:

gcc -g -O2 -Wall -o .libs/perfchart.png perfchart.o cgi.o  -L/usr/lib/mysql /usr/lib/mysql/libmysqlclient.a -lcrypt -lnsl -lm -lz -lc -lnss_files -lnss_dns -lresolv -lglib-2.0 -L/lib -lgd -L/opt/perfparse-0.100.7/libperfparse /opt/perfparse-0.100.7/libperfparse/.libs/libperfparse.so -Wl,--rpath -Wl,/opt/nagios/lib
/usr/lib/gcc-lib/i386-redhat-linux/3.3.3/../../../libgd.a(gd_png.o)(.text+0x37): In function `gdPngErrorHandler':
: undefined reference to `png_get_error_ptr'
/usr/lib/gcc-lib/i386-redhat-linux/3.3.3/../../../libgd.a(gd_png.o)(.text+0xa9): In function `gdPngReadData':
: undefined reference to `png_get_io_ptr'
/usr/lib/gcc-lib/i386-redhat-linux/3.3.3/../../../libgd.a(gd_png.o)(.text+0xe9): In function `gdPngWriteData':

After adding -lpng to the line starting MYSQL_LIBS in cgi/Makefile (before -lz) compilation proceeded sucessfully!

Perhaps someone else knows if there is a bug in the configure script?

Cheers

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 Nick P G Smith
 7 Signal Court, Station Rd, Lingfield, Surrey, RH7 6DY, UK.

 EMAIL: ni...@sm... (nic...@sm...)
 WWW:   http://www.smithnet.ods.org/ 
 WAP:   http://wap.smithnet.ods.org/ 
 TEL:   +44 (0)1342 835098
 MOB:   +44 (0)7810 445470
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 "In the long run ... we are all dead" - JMK
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

RE: [Perfparse-users] Trouble patching check_nt to get perf data

[Cook, G. <GW...@ma...>]

Clif,
It's been a while since I wrote that patch, and there were originally
some errors in my code that botched the memory check, although it did
enable the perfdata output correctly. However, this patch must be
applied against the original stable release, I don't know how it will
work against a CVS version of the stable code, which is what it appears
as though you've used below.
Also, perfdata and a few other things should be fixed in the latest CVS
version of the 1.4.0-alpha plugins. I would suggest that you use those.
If they don't work for you, send another email to the list, and perhaps
copy the nagiosplug-users list to increase the pool of users that might
be able to assist with the error.

Garry W. Cook, CCNA
Network Infrastructure Manager
MACTEC, Inc. - http://www.mactec.com/
303.308.6228 (Office) - 720.220.1862 (Mobile)

per...@li... wrote:
> First of all, thanks again for PerfParse.  I'm hoping once I get my
> ducks in a row with which plugins to use, etc., I'll replace
> APAN with it.
>=20
> I tried the check_nt plugin with what I assume is the latest
> build, but
> it didn't provide performance data.  I then tried to patch
> check_nt with
> the patch on your site, but receive the following:
> nagios-plugins-r1_3_0-200410041647]# patch plugins/check_nt.c
> check_nt.c.patch patching file plugins/check_nt.c
> Hunk #2 FAILED at 81.
> Hunk #3 FAILED at 140.
> Hunk #4 FAILED at 164.
> Hunk #5 FAILED at 202.
> Hunk #6 FAILED at 223.
> Hunk #7 FAILED at 255.
> Hunk #8 FAILED at 291.
> Hunk #9 succeeded at 406 (offset 54 lines).
> Hunk #10 FAILED at 599.
> Hunk #11 FAILED at 626.
> Hunk #12 FAILED at 636.
> Hunk #13 FAILED at 646.
> Hunk #14 FAILED at 666.
> 12 out of 14 hunks FAILED -- saving rejects to file
> plugins/check_nt.c.rej=20
>=20
> Here's the contents reject file:
> ***************
> *** 78,89 ****
[snip]

Re: [Perfparse-users] Perfparse incorrectly reporting State when using check_disk

[Clif <cj...@cj...>]

You caught me!  While I had updated my plugins locally, I forgot to do 
so on this remote host.  Thanks again!  Great product!

cjs

Ben Clewett wrote:

> Clif,
>
> This is a bug in the plugin.  Which I though had been fixed.  The 
> numbers shown are not the same unit.  The value is 'disk free MB' and 
> the warn/crit are 'disk used MB'.  These cannot be directly compared 
> and therefore return the wrong state.
>
> I have been told by one of plugin developers that there is a version 
> of this plugin which has been fixed.  Can you try downloading the 
> latest snapshot and see if this is correct?
>
> Regards, Ben.
>
>
> Clif wrote:
>
>> When doing <./check_disk -l -w 10% -c 5%>
>> DISK OK - free space: / 31 MB (12%); /boot 90 MB (74%); /disk1 658 MB 
>> (90%); /dev/shm 503 MB (100%); /tmp 450 MB (91%); /usr 1729 MB (43%); 
>> /var 321 MB (32%);| /=30MB;225;237;0;250 /boot=90MB;108;114;0;121 
>> /disk1=657MB;659;696;0;733 /dev/shm=503MB;452;477;0;503 
>> /tmp=450MB;443;468;0;493 /usr=1728MB;3627;3828;0;4030 
>> /var=321MB;909;960;0;1011
>>
>> The plugin and Nagios correctly see that all is good (DISK OK), no 
>> disks have 10% or less free.  However, PerfParse shows /dev/shm and 
>> /tmp to be at Critical and Warning?!
>>
>> Any ideas?
>>
>> cjs
>>
>>
>> -------------------------------------------------------
>> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
>> Use IT products in your business? Tell us what you think of them. 
>> Give us
>> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find 
>> out more
>> http://productguide.itmanagersjournal.com/guidepromo.tmpl
>> _______________________________________________
>> Perfparse-users mailing list
>> Per...@li...
>> https://lists.sourceforge.net/lists/listinfo/perfparse-users
>>

Re: [Perfparse-users] Perfparse incorrectly reporting State when using check_disk

[Ben C. <Be...@cl...>]

Clif,

This is a bug in the plugin.  Which I though had been fixed.  The 
numbers shown are not the same unit.  The value is 'disk free MB' and 
the warn/crit are 'disk used MB'.  These cannot be directly compared and 
therefore return the wrong state.

I have been told by one of plugin developers that there is a version of 
this plugin which has been fixed.  Can you try downloading the latest 
snapshot and see if this is correct?

Regards, Ben.


Clif wrote:

> When doing <./check_disk -l -w 10% -c 5%>
> DISK OK - free space: / 31 MB (12%); /boot 90 MB (74%); /disk1 658 MB 
> (90%); /dev/shm 503 MB (100%); /tmp 450 MB (91%); /usr 1729 MB (43%); 
> /var 321 MB (32%);| /=30MB;225;237;0;250 /boot=90MB;108;114;0;121 
> /disk1=657MB;659;696;0;733 /dev/shm=503MB;452;477;0;503 
> /tmp=450MB;443;468;0;493 /usr=1728MB;3627;3828;0;4030 
> /var=321MB;909;960;0;1011
> 
> The plugin and Nagios correctly see that all is good (DISK OK), no disks 
> have 10% or less free.  However, PerfParse shows /dev/shm and /tmp to be 
> at Critical and Warning?!
> 
> Any ideas?
> 
> cjs
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> Perfparse-users mailing list
> Per...@li...
> https://lists.sourceforge.net/lists/listinfo/perfparse-users
> 

Re: [Perfparse-users] Perfparse incorrectly reporting State when using check_disk

[Yves M. <yme...@li...>]

> Clif a =E9crit :
>
>> When doing <./check_disk -l -w 10% -c 5%> DISK OK - free space: / 31
>>  MB (12%); /boot 90 MB (74%); /disk1 658 MB (90%); /dev/shm 503 MB
>> (100%); /tmp 450 MB (91%); /usr 1729 MB (43%); /var 321 MB (32%);|
>> /=3D30MB;225;237;0;250 /boot=3D90MB;108;114;0;121
>> /disk1=3D657MB;659;696;0;733 /dev/shm=3D503MB;452;477;0;503
>> /tmp=3D450MB;443;468;0;493 /usr=3D1728MB;3627;3828;0;4030
>> /var=3D321MB;909;960;0;1011
>>
>> The plugin and Nagios correctly see that all is good (DISK OK), no
>> disks have 10% or less free.  However, PerfParse shows /dev/shm and
>> /tmp to be at Critical and Warning?!
>>
>> Any ideas?
> yes, i've seen it. it seems to me, perfparse check only if we are above
> a limit and not under (or something like that). i've seen this strange
> effect on some other plugins but doesn't have time to investigate more
> for now.

When you don't specify the lower limit, the number is the higher limit an=
d the lower
limit is 0 (see the plugin specs).

In Perfarse, there is a limitation with limits : we can parse and store o=
nly one number
and consider it as the higher limit. I need to investigate to see if vers=
ions until
0.100.X consider the lower limit as -infinite or as 0.

In perfparse-0.101.X we don't have that limitation in the parser any more=
. We will keep
that limitation in the database schema for a while because we cannot do e=
verything at
the same time :)
However, fixing this limitation is in our high priorities, with reducing =
the database
size and with having a better client/server support than just accessing t=
he database
directly from any machine.

Before that we change it, try to avoid plugins that return inversed value=
s (as free
space, free memory, free candy...) and only have plugins that return WARN=
 or CRIT with
high values.
Help is always welcome, and now, help would be particularly appreciated f=
or beta-testing
perfparse-0.101.0ymX from http://ymettier.chez.tiscali.fr/perfparse-devel=
/index.php
(warning : I'm very active and I can release more than 1 version a day :)
Read doc/UPGRADE that is the only documentation about what changed.

Yves

--=20
- Homepage    - http://ymettier.free.fr - http://www.logicacmg.com -
- GPG key     - http://ymettier.free.fr/gpg.txt                    -
- Maitretarot - http://www.nongnu.org/maitretarot/                 -
- GTKtalog    - http://www.nongnu.org/gtktalog/                    -

Re: [Perfparse-users] Perfparse incorrectly reporting State when using check_disk

[Julien T. <jul...@ly...>]

Clif a =E9crit :

> When doing <./check_disk -l -w 10% -c 5%> DISK OK - free space: / 31
>  MB (12%); /boot 90 MB (74%); /disk1 658 MB (90%); /dev/shm 503 MB=20
> (100%); /tmp 450 MB (91%); /usr 1729 MB (43%); /var 321 MB (32%);|=20
> /=3D30MB;225;237;0;250 /boot=3D90MB;108;114;0;121=20
> /disk1=3D657MB;659;696;0;733 /dev/shm=3D503MB;452;477;0;503=20
> /tmp=3D450MB;443;468;0;493 /usr=3D1728MB;3627;3828;0;4030=20
> /var=3D321MB;909;960;0;1011
>=20
> The plugin and Nagios correctly see that all is good (DISK OK), no=20
> disks have 10% or less free.  However, PerfParse shows /dev/shm and=20
> /tmp to be at Critical and Warning?!
>=20
> Any ideas?
yes, i've seen it. it seems to me, perfparse check only if we are above
a limit and not under (or something like that). i've seen this strange
effect on some other plugins but doesn't have time to investigate more
for now.

Regards

		Julien

[Perfparse-users] After moving to the latest plugins, check_smtp is giving PerfParse fits

[Clif J. S. <per...@cj...>]

When using today's snapshot of the 1.4.0 plugin for check_smtp the 
output is:
SMTP OK - 0.013 sec. response time|time=12684us;2;4;0
which is put into the serviceperf.log as:
1097088461      defender        SMTP    SMTP OK - 0.013 sec. response 
time      OK      time=13027us;2;4;0
which causes PerfParse to report that the Time State is Critical

the previous output was
SMTP OK - 0.013 sec. response time|time=12700us;2000000;4000000;0
and
1097085448      defender        SMTP    SMTP OK - 0.013 sec. response 
time      OK      time=12882us;2000000;4000000;0

Is this a "bug" to take to the plugin list or is a "feature" that will 
be incorporated within PerfParse when time allows?

Thanks, Clif

[Perfparse-users] Perfparse incorrectly reporting State when using check_disk

[Clif <cj...@cj...>]

When doing <./check_disk -l -w 10% -c 5%>
DISK OK - free space: / 31 MB (12%); /boot 90 MB (74%); /disk1 658 MB 
(90%); /dev/shm 503 MB (100%); /tmp 450 MB (91%); /usr 1729 MB (43%); 
/var 321 MB (32%);| /=30MB;225;237;0;250 /boot=90MB;108;114;0;121 
/disk1=657MB;659;696;0;733 /dev/shm=503MB;452;477;0;503 
/tmp=450MB;443;468;0;493 /usr=1728MB;3627;3828;0;4030 
/var=321MB;909;960;0;1011

The plugin and Nagios correctly see that all is good (DISK OK), no disks 
have 10% or less free.  However, PerfParse shows /dev/shm and /tmp to be 
at Critical and Warning?!

Any ideas?

cjs

Re: [Perfparse-users] Trouble patching check_nt to get perf data

[Clif J. S. <per...@cj...>]

I'm a complete moron - I just noticed the 1_3_0...  Thanks!

cjs


Cook, Garry wrote:

>That's the correct page. Just make sure you grab the 'HEAD' version,
>which should be the absolute latest version, although not necessarily
>stable. I believe that the version you grabbed was CVS of the old
>plugins (v 1.3.0). I made this assumption based on the name of the
>directory that you were working in,
>nagios-plugins-r1_3_0-200410041647]#.
>
>-g
>
>Clif J. Smith wrote:
>  
>
>>Did I grab the "latest CVS version of the 1.4.0-alpha plugins" by
>>grabbing those listed here:
>>http://nagiosplug.sourceforge.net/snapshot/ 
>>
>>Is there somewhere else they'd be located?  I found that location off
>>of the nagiosplugs web page saying it was the daily snapshot of
>>what's in CVS.
>>
>>cjs
>>
>>
>>
>>Cook, Garry wrote:
>>
>>    
>>
>>>Clif,
>>>It's been a while since I wrote that patch, and there were originally
>>>some errors in my code that botched the memory check, although it did
>>>enable the perfdata output correctly. However, this patch must be
>>>applied against the original stable release, I don't know how it will
>>>work against a CVS version of the stable code, which is what it
>>>appears as though you've used below. Also, perfdata and a few other
>>>things should be fixed in the latest CVS version of the 1.4.0-alpha
>>>plugins. I would suggest that you use those. If they don't work for
>>>you, send another email to the list, and perhaps copy the
>>>nagiosplug-users list to increase the pool of users that might be
>>>able to assist with the error. 
>>>
>>>Garry W. Cook, CCNA
>>>Network Infrastructure Manager
>>>MACTEC, Inc. - http://www.mactec.com/
>>>303.308.6228 (Office) - 720.220.1862 (Mobile)
>>>
>>>per...@li... wrote:
>>>
>>>
>>>      
>>>
>>>>First of all, thanks again for PerfParse.  I'm hoping once I get my
>>>>ducks in a row with which plugins to use, etc., I'll replace
>>>>APAN with it.
>>>>
>>>>I tried the check_nt plugin with what I assume is the latest build,
>>>>but it didn't provide performance data.  I then tried to patch
>>>>check_nt with the patch on your site, but receive the following:
>>>>nagios-plugins-r1_3_0-200410041647]# patch plugins/check_nt.c
>>>>check_nt.c.patch patching file plugins/check_nt.c
>>>>Hunk #2 FAILED at 81.
>>>>Hunk #3 FAILED at 140.
>>>>Hunk #4 FAILED at 164.
>>>>Hunk #5 FAILED at 202.
>>>>Hunk #6 FAILED at 223.
>>>>Hunk #7 FAILED at 255.
>>>>Hunk #8 FAILED at 291.
>>>>Hunk #9 succeeded at 406 (offset 54 lines).
>>>>Hunk #10 FAILED at 599.
>>>>Hunk #11 FAILED at 626.
>>>>Hunk #12 FAILED at 636.
>>>>Hunk #13 FAILED at 646.
>>>>Hunk #14 FAILED at 666.
>>>>12 out of 14 hunks FAILED -- saving rejects to file
>>>>plugins/check_nt.c.rej 
>>>>
>>>>Here's the contents reject file:
>>>>***************
>>>>*** 78,89 ****
>>>>
>>>>
>>>>        
>>>>
>>>[snip]
>>>      
>>>
>
>  
>

RE: [Perfparse-users] Trouble patching check_nt to get perf data

[Cook, G. <GW...@ma...>]

That's the correct page. Just make sure you grab the 'HEAD' version,
which should be the absolute latest version, although not necessarily
stable. I believe that the version you grabbed was CVS of the old
plugins (v 1.3.0). I made this assumption based on the name of the
directory that you were working in,
nagios-plugins-r1_3_0-200410041647]#.

-g

Clif J. Smith wrote:
> Did I grab the "latest CVS version of the 1.4.0-alpha plugins" by
> grabbing those listed here:
> http://nagiosplug.sourceforge.net/snapshot/=20
>=20
> Is there somewhere else they'd be located?  I found that location off
> of the nagiosplugs web page saying it was the daily snapshot of
> what's in CVS.
>=20
> cjs
>=20
>=20
>=20
> Cook, Garry wrote:
>=20
>> Clif,
>> It's been a while since I wrote that patch, and there were originally
>> some errors in my code that botched the memory check, although it did
>> enable the perfdata output correctly. However, this patch must be
>> applied against the original stable release, I don't know how it will
>> work against a CVS version of the stable code, which is what it
>> appears as though you've used below. Also, perfdata and a few other
>> things should be fixed in the latest CVS version of the 1.4.0-alpha
>> plugins. I would suggest that you use those. If they don't work for
>> you, send another email to the list, and perhaps copy the
>> nagiosplug-users list to increase the pool of users that might be
>> able to assist with the error.=20
>>=20
>> Garry W. Cook, CCNA
>> Network Infrastructure Manager
>> MACTEC, Inc. - http://www.mactec.com/
>> 303.308.6228 (Office) - 720.220.1862 (Mobile)
>>=20
>> per...@li... wrote:
>>=20
>>=20
>>> First of all, thanks again for PerfParse.  I'm hoping once I get my
>>> ducks in a row with which plugins to use, etc., I'll replace
>>> APAN with it.
>>>=20
>>> I tried the check_nt plugin with what I assume is the latest build,
>>> but it didn't provide performance data.  I then tried to patch
>>> check_nt with the patch on your site, but receive the following:
>>> nagios-plugins-r1_3_0-200410041647]# patch plugins/check_nt.c
>>> check_nt.c.patch patching file plugins/check_nt.c
>>> Hunk #2 FAILED at 81.
>>> Hunk #3 FAILED at 140.
>>> Hunk #4 FAILED at 164.
>>> Hunk #5 FAILED at 202.
>>> Hunk #6 FAILED at 223.
>>> Hunk #7 FAILED at 255.
>>> Hunk #8 FAILED at 291.
>>> Hunk #9 succeeded at 406 (offset 54 lines).
>>> Hunk #10 FAILED at 599.
>>> Hunk #11 FAILED at 626.
>>> Hunk #12 FAILED at 636.
>>> Hunk #13 FAILED at 646.
>>> Hunk #14 FAILED at 666.
>>> 12 out of 14 hunks FAILED -- saving rejects to file
>>> plugins/check_nt.c.rej=20
>>>=20
>>> Here's the contents reject file:
>>> ***************
>>> *** 78,89 ****
>>>=20
>>>=20
>> [snip]

Re: [Perfparse-users] Trouble patching check_nt to get perf data

[Clif J. S. <per...@cj...>]

Did I grab the "latest CVS version of the 1.4.0-alpha plugins" by 
grabbing those listed here:
http://nagiosplug.sourceforge.net/snapshot/

Is there somewhere else they'd be located?  I found that location off of 
the nagiosplugs web page saying it was the daily snapshot of what's in 
CVS. 

cjs



Cook, Garry wrote:

>Clif,
>It's been a while since I wrote that patch, and there were originally
>some errors in my code that botched the memory check, although it did
>enable the perfdata output correctly. However, this patch must be
>applied against the original stable release, I don't know how it will
>work against a CVS version of the stable code, which is what it appears
>as though you've used below.
>Also, perfdata and a few other things should be fixed in the latest CVS
>version of the 1.4.0-alpha plugins. I would suggest that you use those.
>If they don't work for you, send another email to the list, and perhaps
>copy the nagiosplug-users list to increase the pool of users that might
>be able to assist with the error.
>
>Garry W. Cook, CCNA
>Network Infrastructure Manager
>MACTEC, Inc. - http://www.mactec.com/
>303.308.6228 (Office) - 720.220.1862 (Mobile)
>
>per...@li... wrote:
>  
>
>>First of all, thanks again for PerfParse.  I'm hoping once I get my
>>ducks in a row with which plugins to use, etc., I'll replace
>>APAN with it.
>>
>>I tried the check_nt plugin with what I assume is the latest
>>build, but
>>it didn't provide performance data.  I then tried to patch
>>check_nt with
>>the patch on your site, but receive the following:
>>nagios-plugins-r1_3_0-200410041647]# patch plugins/check_nt.c
>>check_nt.c.patch patching file plugins/check_nt.c
>>Hunk #2 FAILED at 81.
>>Hunk #3 FAILED at 140.
>>Hunk #4 FAILED at 164.
>>Hunk #5 FAILED at 202.
>>Hunk #6 FAILED at 223.
>>Hunk #7 FAILED at 255.
>>Hunk #8 FAILED at 291.
>>Hunk #9 succeeded at 406 (offset 54 lines).
>>Hunk #10 FAILED at 599.
>>Hunk #11 FAILED at 626.
>>Hunk #12 FAILED at 636.
>>Hunk #13 FAILED at 646.
>>Hunk #14 FAILED at 666.
>>12 out of 14 hunks FAILED -- saving rejects to file
>>plugins/check_nt.c.rej 
>>
>>Here's the contents reject file:
>>***************
>>*** 78,89 ****
>>    
>>
>[snip]
>  
>

[Perfparse-users] check_disk_remote plugin -- alpha

[Jeff S. <je...@sk...>]

Here is a first draft of a plugin that checks disk usage on a remote UNIX  
system via rsh or ssh, and returns performance data for each filesystem.   
The highest level of Ok, Warning, or Critical is returned.  Not heavily  
tested, but is working well for me.  Might need to adjust 'df' command for  
some OSes.  My vendors do not allow "Third Party" software of any kind  
installed on my servers, so everything has to be done via ssh.  So, I'm  
slowly re-writing the plugins I need to perform all service checks via  
ssh, and to return performance data.  Posting here since I really wrote it  
for use with Perfparse.  I'm just learning plugin development, so bare  
with me please....

Thanks,
Jeff Scott

Re: [Perfparse-users] Trouble patching check_nt to get perf data

[Ben C. <Be...@cl...>]

Hi Clif,

Sorry but I haven't been involved with this.  If nobody else on this 
list gives you a reply, you may try the mailing list 'nagiosplug-help' 
where I have noticed postings about this plugins.

I do hope you get an answer so that you can replace APAN with PP :)

Regards, Ben.

Clif J. Smith wrote:

> First of all, thanks again for PerfParse.  I'm hoping once I get my 
> ducks in a row with which plugins to use, etc., I'll replace APAN with it.
> 
> I tried the check_nt plugin with what I assume is the latest build, but 
> it didn't provide performance data.  I then tried to patch check_nt with 
> the patch on your site, but receive the following:
> nagios-plugins-r1_3_0-200410041647]# patch plugins/check_nt.c 
> check_nt.c.patch
> patching file plugins/check_nt.c
> Hunk #2 FAILED at 81.
> Hunk #3 FAILED at 140.
> Hunk #4 FAILED at 164.
> Hunk #5 FAILED at 202.
> Hunk #6 FAILED at 223.
> Hunk #7 FAILED at 255.
> Hunk #8 FAILED at 291.
> Hunk #9 succeeded at 406 (offset 54 lines).
> Hunk #10 FAILED at 599.
> Hunk #11 FAILED at 626.
> Hunk #12 FAILED at 636.
> Hunk #13 FAILED at 646.
> Hunk #14 FAILED at 666.
> 12 out of 14 hunks FAILED -- saving rejects to file plugins/check_nt.c.rej
> 
> Here's the contents reject file:
> ***************
> *** 78,89 ****
>      int return_code = STATE_UNKNOWN;
>      char *send_buffer=NULL;
>      char *output_message=NULL;
>      char *temp_string=NULL;
>      char *description=NULL;
> 
>      double total_disk_space=0;
>      double free_disk_space=0;
>      double percent_used_space=0;
>      double mem_commitLimit=0;
>      double mem_commitByte=0;
>      unsigned long utilization;
> --- 81,96 ----
>      int return_code = STATE_UNKNOWN;
>      char *send_buffer=NULL;
>      char *output_message=NULL;
> +   char *perfdata=NULL; // Added for perfdata - GWC - 20040810
>      char *temp_string=NULL;
> +   char *temp_string_perf=NULL; // Added for perfdata - GWC - 20040810
>      char *description=NULL;
> 
>      double total_disk_space=0;
>      double free_disk_space=0;
>      double percent_used_space=0;
> +   double warning_used_space=0; //Added for perfdata - GWC - 20040811
> +   double critical_used_space=0; //Added for perfdata - GWC - 20040811
>      double mem_commitLimit=0;
>      double mem_commitByte=0;
>      unsigned long utilization;
> ***************
> *** 133,138 ****
>                      /* -l parameters is present with only integers */
>                      return_code=STATE_OK;
>                      temp_string = strdup (_("CPU Load"));
>                      /* loop until one of the parameters is wrong or not 
> present */
>                      while (lvalue_list[0+offset]> (unsigned long)0 &&
>                                               
> lvalue_list[0+offset]<=(unsigned long)17280 &&
> --- 140,147 ----
>                      /* -l parameters is present with only integers */
>                      return_code=STATE_OK;
>                      temp_string = strdup (_("CPU Load"));
> +       temp_string_perf = strdup (_(" ")); // Added for perfdata - 
> 20040810 - GWC
> +
>                      /* loop until one of the parameters is wrong or not 
> present */
>                      while (lvalue_list[0+offset]> (unsigned long)0 &&
>                                               
> lvalue_list[0+offset]<=(unsigned long)17280 &&
> ***************
> *** 155,164 ****
> 
>                              asprintf(&output_message,_(" %lu%% (%lu min 
> average)"), utilization, lvalue_list[0+offset]);
>                              
> asprintf(&temp_string,"%s%s",temp_string,output_message);
>                              offset+=3;      /* move across the array */
>                      }
>                      if (strlen(temp_string)>10)  /* we had at least one 
> loop */
> -                               output_message = strdup (temp_string);
>                      else
>                              output_message = strdup (_("not enough 
> values for -l parameters"));
>              }
> --- 164,178 ----
> 
>                              asprintf(&output_message,_(" %lu%% (%lu min 
> average)"), utilization, lvalue_list[0+offset]);
>                              
> asprintf(&temp_string,"%s%s",temp_string,output_message);
> +       asprintf(&perfdata,_(" '%lu min avg Load'=%lu%%;%lu;%lu;0;100"), 
> lvalue_list[0+offset], utilization,
> +                lvalue_list[1+offset], lvalue_list[2+offset]); // Added 
> for perfdata - GWC - 20040810
> +       asprintf(&temp_string_perf,"%s%s",temp_string_perf,perfdata); // 
> Added for perfdata - GWC - 20040810
>                              offset+=3;      /* move across the array */
>                      }
> +
>                      if (strlen(temp_string)>10)  /* we had at least one 
> loop */
> +       output_message = strdup (temp_string),
> +         perfdata = temp_string_perf; // Added for perfdata - GWC - 
> 20040810
>                      else
>                              output_message = strdup (_("not enough 
> values for -l parameters"));
>              }
> ***************
> *** 188,199 ****
>                      free_disk_space=atof(strtok(recv_buffer,"&"));
>                      total_disk_space=atof(strtok(NULL,"&"));
>                      percent_used_space = ((total_disk_space - 
> free_disk_space) / total_disk_space) * 100;
> 
>                      if (free_disk_space>=0) {
>                              asprintf(&temp_string,_("%s:\\ - total: 
> %.2f Gb - used: %.2f Gb (%.0f%%) - free %.2f Gb (%.0f%%)"),
> -                                                                
> value_list, total_disk_space / 1073741824, (total_disk_space - 
> free_disk_space) / 1073741824, percent_used_space,
> -                                                                
> free_disk_space / 1073741824, (free_disk_space / total_disk_space)*100);
> -
> 
>                              if(check_critical_value==TRUE && 
> percent_used_space >= critical_value)
>                                      return_code=STATE_CRITICAL;
> --- 202,219 ----
>                      free_disk_space=atof(strtok(recv_buffer,"&"));
>                      total_disk_space=atof(strtok(NULL,"&"));
>                      percent_used_space = ((total_disk_space - 
> free_disk_space) / total_disk_space) * 100;
> +       warning_used_space = ((float)warning_value / 100) * 
> total_disk_space; // Added for perfdata - 20040816 - GWC
> +       critical_used_space = ((float)critical_value / 100) * 
> total_disk_space; // Added for perfdata - 20040816 - GWC
> +       //warning_used_space = warning_value; // Added for perfdata - 
> 20040811 - GWC
> +       //critical_used_space = critical_value; // Added for perfdata - 
> 20040811 - GWC
> 
>                      if (free_disk_space>=0) {
>                              asprintf(&temp_string,_("%s:\\ - total: 
> %.2f Gb - used: %.2f Gb (%.0f%%) - free %.2f Gb (%.0f%%)"),
> +                value_list, total_disk_space / 1073741824, 
> (total_disk_space - free_disk_space) / 1073741824,
> +                percent_used_space, free_disk_space / 1073741824, 
> (free_disk_space / total_disk_space)*100);
> +       asprintf(&temp_string_perf,_("'%s:\\ Used 
> Space'=%.2fGb;%.2f;%.2f;0.00;%.2f"), value_list,
> +                (total_disk_space - free_disk_space) / 1073741824, 
> warning_used_space / 1073741824,
> +                critical_used_space / 1073741824, total_disk_space / 
> 1073741824); // Added for perfdata - GWC - 20040811
> 
>                              if(check_critical_value==TRUE && 
> percent_used_space >= critical_value)
>                                      return_code=STATE_CRITICAL;
> ***************
> *** 203,208 ****
>                                      return_code=STATE_OK;
> 
>                              output_message = strdup (temp_string);
>                      }
>                      else {
>                              output_message = strdup (_("Free disk space 
> : Invalid drive "));
> --- 223,229 ----
>                                      return_code=STATE_OK;
> 
>                              output_message = strdup (temp_string);
> +       perfdata = temp_string_perf; // Added for perfdata - GWC - 20040810
>                      }
>                      else {
>                              output_message = strdup (_("Free disk space 
> : Invalid drive "));
> ***************
> *** 234,242 ****
>              mem_commitLimit=atof(strtok(recv_buffer,"&"));
>              mem_commitByte=atof(strtok(NULL,"&"));
>              percent_used_space = (mem_commitByte / mem_commitLimit) * 100;
>              asprintf(&output_message,_("Memory usage: total:%.2f Mb - 
> used: %.2f Mb (%.0f%%) - free: %.2f Mb (%.0f%%)"),
> -                       mem_commitLimit / 1048576, mem_commitByte / 
> 1048567, percent_used_space,
> -                       (mem_commitLimit - mem_commitByte) / 1048576, 
> (mem_commitLimit - mem_commitByte) / mem_commitLimit * 100);
> 
>              return_code=STATE_OK;
>              if(check_critical_value==TRUE && percent_used_space >= 
> critical_value)
> --- 255,271 ----
>              mem_commitLimit=atof(strtok(recv_buffer,"&"));
>              mem_commitByte=atof(strtok(NULL,"&"));
>              percent_used_space = (mem_commitByte / mem_commitLimit) * 100;
> +     warning_used_space = ((float)warning_value / 100) * 
> mem_commitLimit; // Fixed for perfdata - 20040816 - GWC
> +     critical_used_space = ((float)critical_value / 100) * 
> mem_commitLimit; // Fixed for perfdata - 20040816 - GWC
> +     //warning_used_space = warning_value; // Added for perfdata - 
> 20040811 - GWC
> +     //critical_used_space = critical_value; // Added for perfdata - 
> 20040811 - GWC
> +     // Changed divisor in following line from 1048567 to 3044515 to 
> accurately reflect memory size
>              asprintf(&output_message,_("Memory usage: total:%.2f Mb - 
> used: %.2f Mb (%.0f%%) - free: %.2f Mb (%.0f%%)"),
> +            mem_commitLimit / 3044515, mem_commitByte / 3044515, 
> percent_used_space,
> +            (mem_commitLimit - mem_commitByte) / 3044515, 
> (mem_commitLimit - mem_commitByte) / mem_commitLimit * 100);
> +     asprintf(&perfdata,_("'Memory usage'=%.2fMb;%.2f;%.2f;0.00;%.2f"), 
> mem_commitByte / 3044515,
> +            warning_used_space / 3044515, critical_used_space / 
> 3044515, mem_commitLimit / 3044515);
> +     // Added for perfdata - 20040811 - GWC
> 
>              return_code=STATE_OK;
>              if(check_critical_value==TRUE && percent_used_space >= 
> critical_value)
> ***************
> *** 262,267 ****
>                              asprintf(&output_message, "%.f", 
> counter_value);
>                      else
>                              asprintf(&output_message,"%s = %.f",  
> description, counter_value);
> 
>                      if (critical_value > warning_value) {        /* 
> Normal thresholds */
>                              if(check_critical_value==TRUE && 
> counter_value >= critical_value)
> --- 291,297 ----
>                              asprintf(&output_message, "%.f", 
> counter_value);
>                      else
>                              asprintf(&output_message,"%s = %.f",  
> description, counter_value);
> +       asprintf(&perfdata,"'%s'=%.f",  description, counter_value); // 
> Added for perfdata - 20040811 - GWC
> 
>                      if (critical_value > warning_value) {        /* 
> Normal thresholds */
>                              if(check_critical_value==TRUE && 
> counter_value >= critical_value)
> ***************
> *** 567,574 ****
>      print_revision(progname,"$Revision: 1.21 $");
>      printf (_("\
> Copyright (c) 2000 Yves Rubin (ru...@ya...)\n\n\
> This plugin collects data from the NSClient service running on a\n\
> - Windows NT/2000/XP server.\n\n"));
>      print_usage();
>  printf (_("\nOptions:\n\
> -H, --hostname=HOST\n\
> --- 599,608 ----
>      print_revision(progname,"$Revision: 1.21 $");
>      printf (_("\
> Copyright (c) 2000 Yves Rubin (ru...@ya...)\n\n\
> + 20040811 - Edited to add Performance data output\n\
> +            Garry W. Cook (na...@co...)\n\n\
> This plugin collects data from the NSClient service running on a\n\
> + Windows NT/2000/XP server.\n\\n"));
>      print_usage();
>  printf (_("\nOptions:\n\
> -H, --hostname=HOST\n\
> ***************
> *** 592,599 ****
> -v, --variable=STRING\n\
>  Variable to check.  Valid variables are:\n"));
>  printf (_("\
> -    CLIENTVERSION = Get the NSClient version\n\
> -      If -l <version> is specified, will return warning if versions 
> differ.\n"));
>  printf (_("\
>   CPULOAD = Average CPU load on last x minutes.\n\
>     Request a -l parameter with the following syntax:\n\
> --- 626,633 ----
> -v, --variable=STRING\n\
>  Variable to check.  Valid variables are:\n"));
>  printf (_("\
> +    CLIENTVERSION * = Get the NSClient version\n\
> +      If -l <version> is specified, will return warning if versions 
> differ.\n")); // Edited for perfdata - GWC - 20040811
>  printf (_("\
>   CPULOAD = Average CPU load on last x minutes.\n\
>     Request a -l parameter with the following syntax:\n\
> ***************
> *** 602,609 ****
>     Thresholds are percentage and up to 10 requests can be done in one 
> shot.\n\
>     ie: -l 60,90,95,120,90,95\n"));
>  printf (_("\
> -    UPTIME = Get the uptime of the machine.\n\
> -      No specific parameters. No warning or critical threshold\n"));
>  printf (_("\
>   USEDDISKSPACE = Size and percentage of disk use.\n\
>     Request a -l parameter containing the drive letter only.\n\
> --- 636,643 ----
>     Thresholds are percentage and up to 10 requests can be done in one 
> shot.\n\
>     ie: -l 60,90,95,120,90,95\n"));
>  printf (_("\
> +    UPTIME * = Get the uptime of the machine.\n\
> +      No specific parameters. No warning or critical threshold\n")); // 
> Edited for perfdata - GWC - 20040811
>  printf (_("\
>   USEDDISKSPACE = Size and percentage of disk use.\n\
>     Request a -l parameter containing the drive letter only.\n\
> ***************
> *** 612,627 ****
>   MEMUSE = Memory use.\n\
>     Warning and critical thresholds can be specified with -w and -c.\n"));
>  printf (_("\
> -    SERVICESTATE = Check the state of one or several services.\n\
>     Request a -l parameters with the following syntax:\n\
>     -l <service1>,<service2>,<service3>,...\n\
>     You can specify -d SHOWALL in case you want to see working services\n\
> -                in the returned string.\n"));
>  printf (_("\
> -    PROCSTATE = Check if one or several process are running.\n\
> -      Same syntax as SERVICESTATE.\n"));
>  printf (_("\
> -    COUNTER = Check any performance counter of Windows NT/2000.\n\
>     Request a -l parameters with the following syntax:\n\
>               -l \"\\\\<performance object>\\\\counter\",\"<description>\n\
>     The <description> parameter is optional and \n\
> --- 646,661 ----
>   MEMUSE = Memory use.\n\
>     Warning and critical thresholds can be specified with -w and -c.\n"));
>  printf (_("\
> +    SERVICESTATE * = Check the state of one or several services.\n\
>     Request a -l parameters with the following syntax:\n\
>     -l <service1>,<service2>,<service3>,...\n\
>     You can specify -d SHOWALL in case you want to see working services\n\
> +                in the returned string.\n")); // Edited for perfdata - 
> GWC - 20040811
>  printf (_("\
> +    PROCSTATE * = Check if one or several process are running.\n\
> +      Same syntax as SERVICESTATE.\n")); // Edited for perfdata - GWC - 
> 20040811
>  printf (_("\
> +    COUNTER ** = Check any performance counter of Windows NT/2000.\n\
>     Request a -l parameters with the following syntax:\n\
>               -l \"\\\\<performance object>\\\\counter\",\"<description>\n\
>     The <description> parameter is optional and \n\
> ***************
> *** 632,638 ****
>      printf (_("Notes:\n\
> - The NSClient service should be running on the server to get any 
> information\n\
>   (http://nsclient.ready2run.nl).\n\
> -  - Critical thresholds should be lower than warning thresholds\n"));
> }
> 
> 
> --- 666,674 ----
>      printf (_("Notes:\n\
> - The NSClient service should be running on the server to get any 
> information\n\
>   (http://nsclient.ready2run.nl).\n\
> +  - Critical thresholds should be lower than warning thresholds\n\
> +  - * Denotes check variables that do not return Performance Data\n\
> +  - ** A <description> is required to generate Performance Data 
> output\n")); // Edited for perfdata - GWC - 20040811
> }
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> Perfparse-users mailing list
> Per...@li...
> https://lists.sourceforge.net/lists/listinfo/perfparse-users
> 

[Perfparse-users] Trouble patching check_nt to get perf data

[Clif J. S. <per...@cj...>]

First of all, thanks again for PerfParse.  I'm hoping once I get my 
ducks in a row with which plugins to use, etc., I'll replace APAN with it.

I tried the check_nt plugin with what I assume is the latest build, but 
it didn't provide performance data.  I then tried to patch check_nt with 
the patch on your site, but receive the following:
nagios-plugins-r1_3_0-200410041647]# patch plugins/check_nt.c 
check_nt.c.patch
patching file plugins/check_nt.c
Hunk #2 FAILED at 81.
Hunk #3 FAILED at 140.
Hunk #4 FAILED at 164.
Hunk #5 FAILED at 202.
Hunk #6 FAILED at 223.
Hunk #7 FAILED at 255.
Hunk #8 FAILED at 291.
Hunk #9 succeeded at 406 (offset 54 lines).
Hunk #10 FAILED at 599.
Hunk #11 FAILED at 626.
Hunk #12 FAILED at 636.
Hunk #13 FAILED at 646.
Hunk #14 FAILED at 666.
12 out of 14 hunks FAILED -- saving rejects to file plugins/check_nt.c.rej

Here's the contents reject file:
***************
*** 78,89 ****
      int return_code = STATE_UNKNOWN;
      char *send_buffer=NULL;
      char *output_message=NULL;
      char *temp_string=NULL;
      char *description=NULL;

      double total_disk_space=0;
      double free_disk_space=0;
      double percent_used_space=0;
      double mem_commitLimit=0;
      double mem_commitByte=0;
      unsigned long utilization;
--- 81,96 ----
      int return_code = STATE_UNKNOWN;
      char *send_buffer=NULL;
      char *output_message=NULL;
+   char *perfdata=NULL; // Added for perfdata - GWC - 20040810
      char *temp_string=NULL;
+   char *temp_string_perf=NULL; // Added for perfdata - GWC - 20040810
      char *description=NULL;

      double total_disk_space=0;
      double free_disk_space=0;
      double percent_used_space=0;
+   double warning_used_space=0; //Added for perfdata - GWC - 20040811
+   double critical_used_space=0; //Added for perfdata - GWC - 20040811
      double mem_commitLimit=0;
      double mem_commitByte=0;
      unsigned long utilization;
***************
*** 133,138 ****
                      /* -l parameters is present with only integers */
                      return_code=STATE_OK;
                      temp_string = strdup (_("CPU Load"));
                      /* loop until one of the parameters is wrong or 
not present */
                      while (lvalue_list[0+offset]> (unsigned long)0 &&
                                               
lvalue_list[0+offset]<=(unsigned long)17280 &&
--- 140,147 ----
                      /* -l parameters is present with only integers */
                      return_code=STATE_OK;
                      temp_string = strdup (_("CPU Load"));
+       temp_string_perf = strdup (_(" ")); // Added for perfdata - 
20040810 - GWC
+
                      /* loop until one of the parameters is wrong or 
not present */
                      while (lvalue_list[0+offset]> (unsigned long)0 &&
                                               
lvalue_list[0+offset]<=(unsigned long)17280 &&
***************
*** 155,164 ****

                              asprintf(&output_message,_(" %lu%% (%lu 
min average)"), utilization, lvalue_list[0+offset]);
                              
asprintf(&temp_string,"%s%s",temp_string,output_message);
                              offset+=3;      /* move across the array */
                      }
                      if (strlen(temp_string)>10)  /* we had at least 
one loop */
-                               output_message = strdup (temp_string);
                      else
                              output_message = strdup (_("not enough 
values for -l parameters"));
              }
--- 164,178 ----

                              asprintf(&output_message,_(" %lu%% (%lu 
min average)"), utilization, lvalue_list[0+offset]);
                              
asprintf(&temp_string,"%s%s",temp_string,output_message);
+       asprintf(&perfdata,_(" '%lu min avg Load'=%lu%%;%lu;%lu;0;100"), 
lvalue_list[0+offset], utilization,
+                lvalue_list[1+offset], lvalue_list[2+offset]); // Added 
for perfdata - GWC - 20040810
+       asprintf(&temp_string_perf,"%s%s",temp_string_perf,perfdata); // 
Added for perfdata - GWC - 20040810
                              offset+=3;      /* move across the array */
                      }
+
                      if (strlen(temp_string)>10)  /* we had at least 
one loop */
+       output_message = strdup (temp_string),
+         perfdata = temp_string_perf; // Added for perfdata - GWC - 
20040810
                      else
                              output_message = strdup (_("not enough 
values for -l parameters"));
              }
***************
*** 188,199 ****
                      free_disk_space=atof(strtok(recv_buffer,"&"));
                      total_disk_space=atof(strtok(NULL,"&"));
                      percent_used_space = ((total_disk_space - 
free_disk_space) / total_disk_space) * 100;

                      if (free_disk_space>=0) {
                              asprintf(&temp_string,_("%s:\\ - total: 
%.2f Gb - used: %.2f Gb (%.0f%%) - free %.2f Gb (%.0f%%)"),
-                                                                
value_list, total_disk_space / 1073741824, (total_disk_space - 
free_disk_space) / 1073741824, percent_used_space,
-                                                                
free_disk_space / 1073741824, (free_disk_space / total_disk_space)*100);
-

                              if(check_critical_value==TRUE && 
percent_used_space >= critical_value)
                                      return_code=STATE_CRITICAL;
--- 202,219 ----
                      free_disk_space=atof(strtok(recv_buffer,"&"));
                      total_disk_space=atof(strtok(NULL,"&"));
                      percent_used_space = ((total_disk_space - 
free_disk_space) / total_disk_space) * 100;
+       warning_used_space = ((float)warning_value / 100) * 
total_disk_space; // Added for perfdata - 20040816 - GWC
+       critical_used_space = ((float)critical_value / 100) * 
total_disk_space; // Added for perfdata - 20040816 - GWC
+       //warning_used_space = warning_value; // Added for perfdata - 
20040811 - GWC
+       //critical_used_space = critical_value; // Added for perfdata - 
20040811 - GWC

                      if (free_disk_space>=0) {
                              asprintf(&temp_string,_("%s:\\ - total: 
%.2f Gb - used: %.2f Gb (%.0f%%) - free %.2f Gb (%.0f%%)"),
+                value_list, total_disk_space / 1073741824, 
(total_disk_space - free_disk_space) / 1073741824,
+                percent_used_space, free_disk_space / 1073741824, 
(free_disk_space / total_disk_space)*100);
+       asprintf(&temp_string_perf,_("'%s:\\ Used 
Space'=%.2fGb;%.2f;%.2f;0.00;%.2f"), value_list,
+                (total_disk_space - free_disk_space) / 1073741824, 
warning_used_space / 1073741824,
+                critical_used_space / 1073741824, total_disk_space / 
1073741824); // Added for perfdata - GWC - 20040811

                              if(check_critical_value==TRUE && 
percent_used_space >= critical_value)
                                      return_code=STATE_CRITICAL;
***************
*** 203,208 ****
                                      return_code=STATE_OK;

                              output_message = strdup (temp_string);
                      }
                      else {
                              output_message = strdup (_("Free disk 
space : Invalid drive "));
--- 223,229 ----
                                      return_code=STATE_OK;

                              output_message = strdup (temp_string);
+       perfdata = temp_string_perf; // Added for perfdata - GWC - 20040810
                      }
                      else {
                              output_message = strdup (_("Free disk 
space : Invalid drive "));
***************
*** 234,242 ****
              mem_commitLimit=atof(strtok(recv_buffer,"&"));
              mem_commitByte=atof(strtok(NULL,"&"));
              percent_used_space = (mem_commitByte / mem_commitLimit) * 
100;
              asprintf(&output_message,_("Memory usage: total:%.2f Mb - 
used: %.2f Mb (%.0f%%) - free: %.2f Mb (%.0f%%)"),
-                       mem_commitLimit / 1048576, mem_commitByte / 
1048567, percent_used_space,
-                       (mem_commitLimit - mem_commitByte) / 1048576, 
(mem_commitLimit - mem_commitByte) / mem_commitLimit * 100);

              return_code=STATE_OK;
              if(check_critical_value==TRUE && percent_used_space >= 
critical_value)
--- 255,271 ----
              mem_commitLimit=atof(strtok(recv_buffer,"&"));
              mem_commitByte=atof(strtok(NULL,"&"));
              percent_used_space = (mem_commitByte / mem_commitLimit) * 
100;
+     warning_used_space = ((float)warning_value / 100) * 
mem_commitLimit; // Fixed for perfdata - 20040816 - GWC
+     critical_used_space = ((float)critical_value / 100) * 
mem_commitLimit; // Fixed for perfdata - 20040816 - GWC
+     //warning_used_space = warning_value; // Added for perfdata - 
20040811 - GWC
+     //critical_used_space = critical_value; // Added for perfdata - 
20040811 - GWC
+     // Changed divisor in following line from 1048567 to 3044515 to 
accurately reflect memory size
              asprintf(&output_message,_("Memory usage: total:%.2f Mb - 
used: %.2f Mb (%.0f%%) - free: %.2f Mb (%.0f%%)"),
+            mem_commitLimit / 3044515, mem_commitByte / 3044515, 
percent_used_space,
+            (mem_commitLimit - mem_commitByte) / 3044515, 
(mem_commitLimit - mem_commitByte) / mem_commitLimit * 100);
+     asprintf(&perfdata,_("'Memory usage'=%.2fMb;%.2f;%.2f;0.00;%.2f"), 
mem_commitByte / 3044515,
+            warning_used_space / 3044515, critical_used_space / 
3044515, mem_commitLimit / 3044515);
+     // Added for perfdata - 20040811 - GWC

              return_code=STATE_OK;
              if(check_critical_value==TRUE && percent_used_space >= 
critical_value)
***************
*** 262,267 ****
                              asprintf(&output_message, "%.f", 
counter_value);
                      else
                              asprintf(&output_message,"%s = %.f",  
description, counter_value);

                      if (critical_value > warning_value) {        /* 
Normal thresholds */
                              if(check_critical_value==TRUE && 
counter_value >= critical_value)
--- 291,297 ----
                              asprintf(&output_message, "%.f", 
counter_value);
                      else
                              asprintf(&output_message,"%s = %.f",  
description, counter_value);
+       asprintf(&perfdata,"'%s'=%.f",  description, counter_value); // 
Added for perfdata - 20040811 - GWC

                      if (critical_value > warning_value) {        /* 
Normal thresholds */
                              if(check_critical_value==TRUE && 
counter_value >= critical_value)
***************
*** 567,574 ****
      print_revision(progname,"$Revision: 1.21 $");
      printf (_("\
Copyright (c) 2000 Yves Rubin (ru...@ya...)\n\n\
This plugin collects data from the NSClient service running on a\n\
- Windows NT/2000/XP server.\n\n"));
      print_usage();
  printf (_("\nOptions:\n\
-H, --hostname=HOST\n\
--- 599,608 ----
      print_revision(progname,"$Revision: 1.21 $");
      printf (_("\
Copyright (c) 2000 Yves Rubin (ru...@ya...)\n\n\
+ 20040811 - Edited to add Performance data output\n\
+            Garry W. Cook (na...@co...)\n\n\
This plugin collects data from the NSClient service running on a\n\
+ Windows NT/2000/XP server.\n\\n"));
      print_usage();
  printf (_("\nOptions:\n\
-H, --hostname=HOST\n\
***************
*** 592,599 ****
-v, --variable=STRING\n\
  Variable to check.  Valid variables are:\n"));
  printf (_("\
-    CLIENTVERSION = Get the NSClient version\n\
-      If -l <version> is specified, will return warning if versions 
differ.\n"));
  printf (_("\
   CPULOAD = Average CPU load on last x minutes.\n\
     Request a -l parameter with the following syntax:\n\
--- 626,633 ----
-v, --variable=STRING\n\
  Variable to check.  Valid variables are:\n"));
  printf (_("\
+    CLIENTVERSION * = Get the NSClient version\n\
+      If -l <version> is specified, will return warning if versions 
differ.\n")); // Edited for perfdata - GWC - 20040811
  printf (_("\
   CPULOAD = Average CPU load on last x minutes.\n\
     Request a -l parameter with the following syntax:\n\
***************
*** 602,609 ****
     Thresholds are percentage and up to 10 requests can be done in one 
shot.\n\
     ie: -l 60,90,95,120,90,95\n"));
  printf (_("\
-    UPTIME = Get the uptime of the machine.\n\
-      No specific parameters. No warning or critical threshold\n"));
  printf (_("\
   USEDDISKSPACE = Size and percentage of disk use.\n\
     Request a -l parameter containing the drive letter only.\n\
--- 636,643 ----
     Thresholds are percentage and up to 10 requests can be done in one 
shot.\n\
     ie: -l 60,90,95,120,90,95\n"));
  printf (_("\
+    UPTIME * = Get the uptime of the machine.\n\
+      No specific parameters. No warning or critical threshold\n")); // 
Edited for perfdata - GWC - 20040811
  printf (_("\
   USEDDISKSPACE = Size and percentage of disk use.\n\
     Request a -l parameter containing the drive letter only.\n\
***************
*** 612,627 ****
   MEMUSE = Memory use.\n\
     Warning and critical thresholds can be specified with -w and -c.\n"));
  printf (_("\
-    SERVICESTATE = Check the state of one or several services.\n\
     Request a -l parameters with the following syntax:\n\
     -l <service1>,<service2>,<service3>,...\n\
     You can specify -d SHOWALL in case you want to see working services\n\
-                in the returned string.\n"));
  printf (_("\
-    PROCSTATE = Check if one or several process are running.\n\
-      Same syntax as SERVICESTATE.\n"));
  printf (_("\
-    COUNTER = Check any performance counter of Windows NT/2000.\n\
     Request a -l parameters with the following syntax:\n\
               -l \"\\\\<performance 
object>\\\\counter\",\"<description>\n\
     The <description> parameter is optional and \n\
--- 646,661 ----
   MEMUSE = Memory use.\n\
     Warning and critical thresholds can be specified with -w and -c.\n"));
  printf (_("\
+    SERVICESTATE * = Check the state of one or several services.\n\
     Request a -l parameters with the following syntax:\n\
     -l <service1>,<service2>,<service3>,...\n\
     You can specify -d SHOWALL in case you want to see working services\n\
+                in the returned string.\n")); // Edited for perfdata - 
GWC - 20040811
  printf (_("\
+    PROCSTATE * = Check if one or several process are running.\n\
+      Same syntax as SERVICESTATE.\n")); // Edited for perfdata - GWC - 
20040811
  printf (_("\
+    COUNTER ** = Check any performance counter of Windows NT/2000.\n\
     Request a -l parameters with the following syntax:\n\
               -l \"\\\\<performance 
object>\\\\counter\",\"<description>\n\
     The <description> parameter is optional and \n\
***************
*** 632,638 ****
      printf (_("Notes:\n\
 - The NSClient service should be running on the server to get any 
information\n\
   (http://nsclient.ready2run.nl).\n\
-  - Critical thresholds should be lower than warning thresholds\n"));
}


--- 666,674 ----
      printf (_("Notes:\n\
 - The NSClient service should be running on the server to get any 
information\n\
   (http://nsclient.ready2run.nl).\n\
+  - Critical thresholds should be lower than warning thresholds\n\
+  - * Denotes check variables that do not return Performance Data\n\
+  - ** A <description> is required to generate Performance Data 
output\n")); // Edited for perfdata - GWC - 20040811
}

Re: [Perfparse-users] RE: RES: Warn values are not going into database

[Clif S. <cj...@cj...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
 
No, I'm not experiencing the problems any more.  I had seen some
graphs at some point that showed the warn/crit thresholds as
horizontal lines on each graph.  Now I realize it's been changed to
only show as actual lines within the graph when the thresholds are
reached.

cjs

Ben Clewett wrote:

| Clif,
|
| This problem was (allegedly) fixed some time ago.  Are you still
| experiencing this problem?
|
| I also invite you to upgrade to Yves new parser.  This uses a new
| and better parser, which may fix any problems you have.
|
| Sorry about the lines not being shown.  There has been a lot of
| debate about how to scale the graphs, and no one option suits all
| users:
|
| 1. From Min to Max
| 2. From Zero to largest value in the time range.
| 3. From Zero to Critical value.
| 4. From Zero to the highest of the above.
|
| At the moment 1 is used if there is a range, otherwise 2.
|
| In future versions, all options will be present, and the system will
| remember your own default.  Watch this space!
|
| Regards, Ben.
|
|
| Clif J. Smith wrote:
|
|> Never mind.  I was thinking the Warn/Crit lines would always be
|> shown as horizontal whether reached or not.  After testing, I see
|> they only show as part of the graph when reached.
|>
|> cjs
|>
|>
|> Clif J. Smith wrote:
|>
|>> I just installed v0.100.6 and I'm having the same issue.  I did
|>> tried the hack to no avail, although the settings were already
|>> updated, I just put them in the same order.  Any ideas?
|>>
|>> cjs
|>>
|>> From: Paulo Afonso Graner Fessel <paulo@pr...>
|>> RES: Warn values are not going into database  2004-08-13 13:15
|>>
|>> Ultra-quick hack that seems to solve my problem:
|>>
|>> In perfparse/perfparse.c:
|>>
|>> #define TPERFDATA_MIN   2
|>> #define TPERFDATA_MAX   3
|>> #define TPERFDATA_WARN  0
|>> #define TPERFDATA_CRIT  1
|>> #define TPERFDATA_VALUE 4
|>>
|>> instead of
|>>
|>> #define TPERFDATA_MIN   0
|>> #define TPERFDATA_MAX   1
|>> #define TPERFDATA_WARN  2
|>> #define TPERFDATA_CRIT  3
|>> #define TPERFDATA_VALUE 4
|>>
|>> The lines on the database now show
|>>
|>>
|>>
+------------+---------------------+--------+---------------------+---------+--------+----------+--------+
|>>
|>>  | host_name | service_description | metric | ctime              
|>> | value   | warn   |
|>> critical | state  |
|>>
|>>
+------------+---------------------+--------+---------------------+---------+--------+----------+--------+
|>>
|>>  | nagioslab | /dev/vg00/rootlv    | /      | 2004-08-13 09:58:11
|>> |    5211 |   8567 |    9575 |      0 |
|>>
|>>
+------------+---------------------+--------+---------------------+---------+--------+----------+--------+
|>>
|>>
|>> What, I think, should be the correct behavior.
|>>
|>> []"s
|>> Paulo
|>>
|>>
|>>       "This is not right. This is not even wrong." (Wolfgang
|>> Pauli)        Paulo Fessel
|>> Administrador de Ambiente e Sistemas UNIX     PrimeSys Soluções
|>> Empresariais
|>> Av. Brig. Faria Lima, 1485 - 13° andar
|>> Torre Norte - Pinheiros
|>> 01451-904
|>> São Paulo - SP     paulo.fessel@pr...     tel:
|>> fax:
|>> mobile:     +55 (11) 3038-6554
|>> +55 (11) 3038-6508
|>> +55 (11) 8259-0353         Signature powered by Plaxo
|>> <http://www.plaxo.com/signature>      Want a signature like this?
|>> <http://www.plaxo.com/signature>     Add me to your address book...
|>> <https://www.plaxo.com/add_me?u=8590019246&v0=166225&k0=1601108562>  
|>>   _____     De: Paulo Afonso Graner Fessel
|>>     Enviada em: sexta-feira, 13 de agosto de 2004 09:02
|>>     Para: Cook, Garry; perfparse-users@li...
|>>     Assunto: RES: [Perfparse-users] Warn values are not going into
|>> database
|>>             I wasn"t at the office today, so I"ll try to describe
|>> what"s happening.
|>>         Here"s for example one row of data took from
|>> perfdata_service_bin:
|>>     
|>>
+-----------+---------------------+--------+---------------------+---------+--------+----------+--------+
|>>
|>>     | host_name | service_description | metric |
|>> ctime               | value   | warn   |
|>> critical | state  |
|>>
|>>  
|>>
+-----------+---------------------+--------+---------------------+---------+--------+----------+--------+
|>>
|>>     | nagioslab | /dev/vg00/rootlv    | /      | 2004-07-23
|>> 14:35:10 |    4822 |      0 |   10079 |      0 |
|>>
|>>  
|>>
+-----------+---------------------+--------+---------------------+---------+--------+----------+--------+
|>>
|>>         On the other hand, take a look at the output of check_disk:
|>>         [root@nagioslab libexec]# ./check_disk -w 15% -c 5% -p /
|>>     DISK OK - free space: / 4869 MB (48%);|
|>> /=5211MB;8567;9575;0;10079
|>>         The line recorded at serviceperf.log shows
|>>         1092398291      nagioslab       /dev/vg00/rootlv       
|>> DISK OK - free space: /
|>>     4869 MB (48%):  OK       /=5211MB;8567;9575;0;10079
|>>         Seems that the values that are making into the database
|>> are minimum (0) and maximum
|>> (10079) values instead of warning (10064) and critical (10074)
|>> ones. My patched check_nt
|>> (that provides also perfdata information) also provides evidence
|>> supporting this:
|>>         [root@nagioslab libexec]# ./check_nt -H 10.4.8.135 -v
|>> USEDDISKSPACE -l c -w 85% -c 95%
|>>     c:\ - total: 37.27 Gb - used: 7.31 Gb (20%) - free 29.96 Gb
|>> (80%)|c=7.310GB;31.678;35.404;;37.268
|>>         Now, the line recorded at the database:
|>>     
|>>
+------------+---------------------------+--------+---------------------+---------+--------+----------+--------+
|>>
|>>     | host_name  | service_description       | metric |
|>> ctime               | value   | warn  | critical | state  |
|>>
|>>  
|>>
+------------+---------------------------+--------+---------------------+---------+--------+----------+--------+
|>>
|>>     | bradesk150 | Disco C:                  | c      | 2004-07-23
|>> 15:09:11 |   5.909 |      0
|>> |    37.26 |      0 |
|>>
|>>  
|>>
+------------+---------------------------+--------+---------------------+---------+--------+----------+--------+
|>>
|>>         Again, we see that warn = 0 and critical =- 37.26, when
|>> the correct information should
|>> have been warn = 31.68 and critical = 35.40. Also, as you can see,
|>> both plugins provide
|>> output in the format you mentioned - that is,
|>> "label"=value[UOM];[warn];[crit];[min];[max].
|>>         TIA,
|>>         Paulo Fessel
|>>           "This is not right. This is not even wrong." (Wolfgang
|>> Pauli)        Paulo Fessel
|>> Administrador de Ambiente e Sistemas UNIX     PrimeSys Soluções
|>> Empresariais
|>> Av. Brig. Faria Lima, 1485 - 13° andar
|>> Torre Norte - Pinheiros
|>> 01451-904
|>> São Paulo - SP     paulo.fessel@pr...     tel:
|>> fax:
|>> mobile:     +55 (11) 3038-6554
|>> +55 (11) 3038-6508
|>> +55 (11) 8259-0353         Signature powered by Plaxo
|>> <http://www.plaxo.com/signature>      Want a signature like this?
|>> <http://www.plaxo.com/signature>     Add me to your address book...
|>>
<https://www.plaxo.com/add_me?u=8590019246&v0=166225&k0=1601108562>    
|>>     _____         De: Cook, Garry [mailto:GWCOOK@ma...]
|>>         Enviada em: quinta-feira, 12 de agosto de 2004 12:07
|>>         Para: Paulo Afonso Graner Fessel; perfparse-users@li...
|>>         Assunto: RE: [Perfparse-users] Warn values are not going
|>> into database
|>>                         I"m not sure that I completely understand
|>> your question... What do you mean by "I"m not
|>> including all fields of performance data on plugin output"?
|>>                 Plugin output of performance data should be in the
|>> format
|>> "label"=value[UOM];[warn];[crit];[min];[max]
|>>         Please see
|>> http://nagiosplug.sourceforge.net/developer-guidelines.html#AEN185
|>> for
|>> detailed information.
|>>                 As you can see from the above, some of the
|>> variables are optional (those enclosed in
|>> square brackets). If your performance data does not supply the
|>> warning and critical values,
|>> they will not make it into the database.
|>>
|>>         Garry W. Cook, CCNA
|>>         Network Infrastructure Manager
|>>         MACTEC, Inc. - http://www.mactec.com/
|>>         303.308.6228 (Office) - 720.220.1862 (Mobile)
|>>
|>>             -----Original Message-----
|>>             From: perfparse-users-admin@li...
|>> [mailto:perfparse-users-admin@li...] On Behalf Of Paulo Afonso
|>> Graner Fessel
|>>             Sent: Wednesday, August 11, 2004 2:44 PM
|>>             To: perfparse-users@li...
|>>             Subject: [Perfparse-users] Warn values are not going
|>> into database
|>>                                     Hello, folks.
|>>                         We have noticed today that perfparse is
|>> not inserting the warning values into
|>> perfdata_service_bin table, only the critical ones. So it"s
|>> impossible to graph threshold
|>> lines as warning values are always "0".
|>>                         Does it happen because i"m not including
|>> all fields of performance data on plugin
|>> output? Is it neccessary to include all fields of performance
|>> values on plugin output?
|>>                         []"s
|>>             Paulo Fessel
|>>                   "This is not right. This is not even wrong."
|>> (Wolfgang Pauli)        Paulo Fessel
|>> Administrador de Ambiente e Sistemas UNIX     PrimeSys Soluções
|>> Empresariais
|>> Av. Brig. Faria Lima, 1485 - 13° andar
|>> Torre Norte - Pinheiros
|>> 01451-904
|>> São Paulo - SP     paulo.fessel@pr...     tel:
|>> fax:
|>> mobile:     +55 (11) 3038-6554
|>> +55 (11) 3038-6508
|>> +55 (11) 8259-0353         Signature powered by Plaxo
|>> <http://www.plaxo.com/signature>      Want a signature like this?
|>> <http://www.plaxo.com/signature>     Add me to your address book...
|>>
<https://www.plaxo.com/add_me?u=8590019246&v0=166225&k0=1601108562>    
|>>          
|>>
|>>
|>> -------------------------------------------------------
|>> This SF.net email is sponsored by: IT Product Guide on
|>> ITManagersJournal
|>> Use IT products in your business? Tell us what you think of them.
|>> Give us
|>> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find
|>> out more
|>> http://productguide.itmanagersjournal.com/guidepromo.tmpl
|>> _______________________________________________
|>> Perfparse-users mailing list
|>> Per...@li...
|>> https://lists.sourceforge.net/lists/listinfo/perfparse-users
|>
|>
|>
|>
|>
|>
|> -------------------------------------------------------
|> This SF.net email is sponsored by: IT Product Guide on
|> ITManagersJournal
|> Use IT products in your business? Tell us what you think of them.
|> Give us
|> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find
|> out more
|> http://productguide.itmanagersjournal.com/guidepromo.tmpl
|> _______________________________________________
|> Perfparse-users mailing list
|> Per...@li...
|> https://lists.sourceforge.net/lists/listinfo/perfparse-users
|>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
 
iD8DBQFBYYvAOqA0WuNy3b0RAjOHAJsFEzFJuA9uJ+YZ64sLjypa9GkaxgCdHfSK
5qeO7eFyuSTnG/17tBYzYyE=
=bA4Y
-----END PGP SIGNATURE-----

Re: [Perfparse-users] RE: RES: Warn values are not going into database

[Yves M. <yme...@li...>]

> Clif,
>
> This problem was (allegedly) fixed some time ago.  Are you still
> experiencing this problem?
>
> I also invite you to upgrade to Yves new parser.  This uses a new and
> better parser, which may fix any problems you have.

http://ymettier.chez.tiscali.fr//perfparse-devel/index.php
0.101.0ym11 was released few minutes ago but do not include what Ben did =
for 0.100.7.
0.101.0ym12 will be released soon with Ben's changes :)

There is not much documentation about that new release but there will be =
in the final
0.101.1 :)

Yves

--=20
- Homepage    - http://ymettier.free.fr - http://www.logicacmg.com -
- GPG key     - http://ymettier.free.fr/gpg.txt                    -
- Maitretarot - http://www.nongnu.org/maitretarot/                 -
- GTKtalog    - http://www.nongnu.org/gtktalog/                    -

Re: [Perfparse-users] RE: RES: Warn values are not going into database

[Ben C. <Be...@cl...>]

Clif,

This problem was (allegedly) fixed some time ago.  Are you still=20
experiencing this problem?

I also invite you to upgrade to Yves new parser.  This uses a new and=20
better parser, which may fix any problems you have.

Sorry about the lines not being shown.  There has been a lot of debate=20
about how to scale the graphs, and no one option suits all users:

1. From Min to Max
2. From Zero to largest value in the time range.
3. From Zero to Critical value.
4. From Zero to the highest of the above.

At the moment 1 is used if there is a range, otherwise 2.

In future versions, all options will be present, and the system will=20
remember your own default.  Watch this space!

Regards, Ben.


Clif J. Smith wrote:

> Never mind.  I was thinking the Warn/Crit lines would always be shown a=
s=20
> horizontal whether reached or not.  After testing, I see they only show=
=20
> as part of the graph when reached.
>=20
> cjs
>=20
>=20
> Clif J. Smith wrote:
>=20
>> I just installed v0.100.6 and I'm having the same issue.  I did tried=20
>> the hack to no avail, although the settings were already updated, I=20
>> just put them in the same order.  Any ideas?
>>
>> cjs
>>
>> From: Paulo Afonso Graner Fessel <paulo@pr...>
>> RES: Warn values are not going into database  2004-08-13 13:15
>>
>> Ultra-quick hack that seems to solve my problem:
>>
>> In perfparse/perfparse.c:
>>
>> #define TPERFDATA_MIN   2
>> #define TPERFDATA_MAX   3
>> #define TPERFDATA_WARN  0
>> #define TPERFDATA_CRIT  1
>> #define TPERFDATA_VALUE 4
>>
>> instead of
>>
>> #define TPERFDATA_MIN   0
>> #define TPERFDATA_MAX   1
>> #define TPERFDATA_WARN  2
>> #define TPERFDATA_CRIT  3
>> #define TPERFDATA_VALUE 4
>>
>> The lines on the database now show
>>
>>
>> +------------+---------------------+--------+---------------------+---=
------+--------+----------+--------+=20
>>
>>  | host_name | service_description | metric | ctime               |=20
>> value   | warn   |
>> critical | state  |
>>
>> +------------+---------------------+--------+---------------------+---=
------+--------+----------+--------+=20
>>
>>  | nagioslab | /dev/vg00/rootlv    | /      | 2004-08-13 09:58:11 |   =
=20
>> 5211 |   8567 |    9575 |      0 |
>>
>> +------------+---------------------+--------+---------------------+---=
------+--------+----------+--------+=20
>>
>>
>> What, I think, should be the correct behavior.
>>
>> []"s
>> Paulo
>>
>>
>>       "This is not right. This is not even wrong." (Wolfgang Pauli)   =
=20
>>     Paulo Fessel
>> Administrador de Ambiente e Sistemas UNIX     PrimeSys Solu=E7=F5es=20
>> Empresariais
>> Av. Brig. Faria Lima, 1485 - 13=B0 andar
>> Torre Norte - Pinheiros
>> 01451-904
>> S=E3o Paulo - SP     paulo.fessel@pr...     tel:
>> fax:
>> mobile:     +55 (11) 3038-6554
>> +55 (11) 3038-6508
>> +55 (11) 8259-0353         Signature powered by Plaxo=20
>> <http://www.plaxo.com/signature>      Want a signature like this?
>> <http://www.plaxo.com/signature>     Add me to your address book...
>> <https://www.plaxo.com/add_me?u=3D8590019246&v0=3D166225&k0=3D16011085=
62>  =20
>>
>>   _____     De: Paulo Afonso Graner Fessel
>>     Enviada em: sexta-feira, 13 de agosto de 2004 09:02
>>     Para: Cook, Garry; perfparse-users@li...
>>     Assunto: RES: [Perfparse-users] Warn values are not going into=20
>> database
>>             I wasn"t at the office today, so I"ll try to describe=20
>> what"s happening.
>>         Here"s for example one row of data took from=20
>> perfdata_service_bin:
>>     =20
>> +-----------+---------------------+--------+---------------------+----=
-----+--------+----------+--------+=20
>>
>>     | host_name | service_description | metric | ctime               |=
=20
>> value   | warn   |
>> critical | state  |
>>
>>  =20
>> +-----------+---------------------+--------+---------------------+----=
-----+--------+----------+--------+=20
>>
>>     | nagioslab | /dev/vg00/rootlv    | /      | 2004-07-23 14:35:10=20
>> |    4822 |      0 |   10079 |      0 |
>>
>>  =20
>> +-----------+---------------------+--------+---------------------+----=
-----+--------+----------+--------+=20
>>
>>         On the other hand, take a look at the output of check_disk:
>>         [root@nagioslab libexec]# ./check_disk -w 15% -c 5% -p /
>>     DISK OK - free space: / 4869 MB (48%);| /=3D5211MB;8567;9575;0;100=
79
>>         The line recorded at serviceperf.log shows
>>         1092398291      nagioslab       /dev/vg00/rootlv        DISK=20
>> OK - free space: /
>>     4869 MB (48%):  OK       /=3D5211MB;8567;9575;0;10079
>>         Seems that the values that are making into the database are=20
>> minimum (0) and maximum
>> (10079) values instead of warning (10064) and critical (10074) ones.=20
>> My patched check_nt
>> (that provides also perfdata information) also provides evidence=20
>> supporting this:
>>         [root@nagioslab libexec]# ./check_nt -H 10.4.8.135 -v=20
>> USEDDISKSPACE -l c -w 85% -c 95%
>>     c:\ - total: 37.27 Gb - used: 7.31 Gb (20%) - free 29.96 Gb
>> (80%)|c=3D7.310GB;31.678;35.404;;37.268
>>         Now, the line recorded at the database:
>>     =20
>> +------------+---------------------------+--------+-------------------=
--+---------+--------+----------+--------+=20
>>
>>     | host_name  | service_description       | metric |=20
>> ctime               | value   | warn  | critical | state  |
>>
>>  =20
>> +------------+---------------------------+--------+-------------------=
--+---------+--------+----------+--------+=20
>>
>>     | bradesk150 | Disco C:                  | c      | 2004-07-23=20
>> 15:09:11 |   5.909 |      0
>> |    37.26 |      0 |
>>
>>  =20
>> +------------+---------------------------+--------+-------------------=
--+---------+--------+----------+--------+=20
>>
>>         Again, we see that warn =3D 0 and critical =3D- 37.26, when th=
e=20
>> correct information should
>> have been warn =3D 31.68 and critical =3D 35.40. Also, as you can see,=
=20
>> both plugins provide
>> output in the format you mentioned - that is,=20
>> "label"=3Dvalue[UOM];[warn];[crit];[min];[max].
>>         TIA,
>>         Paulo Fessel
>>           "This is not right. This is not even wrong." (Wolfgang=20
>> Pauli)        Paulo Fessel
>> Administrador de Ambiente e Sistemas UNIX     PrimeSys Solu=E7=F5es=20
>> Empresariais
>> Av. Brig. Faria Lima, 1485 - 13=B0 andar
>> Torre Norte - Pinheiros
>> 01451-904
>> S=E3o Paulo - SP     paulo.fessel@pr...     tel:
>> fax:
>> mobile:     +55 (11) 3038-6554
>> +55 (11) 3038-6508
>> +55 (11) 8259-0353         Signature powered by Plaxo=20
>> <http://www.plaxo.com/signature>      Want a signature like this?
>> <http://www.plaxo.com/signature>     Add me to your address book...
>> <https://www.plaxo.com/add_me?u=3D8590019246&v0=3D166225&k0=3D16011085=
62>    =20
>>  =20
>>   _____         De: Cook, Garry [mailto:GWCOOK@ma...]
>>         Enviada em: quinta-feira, 12 de agosto de 2004 12:07
>>         Para: Paulo Afonso Graner Fessel; perfparse-users@li...
>>         Assunto: RE: [Perfparse-users] Warn values are not going into=20
>> database
>>                         I"m not sure that I completely understand your=
=20
>> question... What do you mean by "I"m not
>> including all fields of performance data on plugin output"?
>>                 Plugin output of performance data should be in the for=
mat
>> "label"=3Dvalue[UOM];[warn];[crit];[min];[max]
>>         Please see=20
>> http://nagiosplug.sourceforge.net/developer-guidelines.html#AEN185 for
>> detailed information.
>>                 As you can see from the above, some of the variables=20
>> are optional (those enclosed in
>> square brackets). If your performance data does not supply the warning=
=20
>> and critical values,
>> they will not make it into the database.
>>
>>         Garry W. Cook, CCNA
>>         Network Infrastructure Manager
>>         MACTEC, Inc. - http://www.mactec.com/
>>         303.308.6228 (Office) - 720.220.1862 (Mobile)
>>
>>             -----Original Message-----
>>             From: perfparse-users-admin@li...
>> [mailto:perfparse-users-admin@li...] On Behalf Of Paulo Afonso Graner=20
>> Fessel
>>             Sent: Wednesday, August 11, 2004 2:44 PM
>>             To: perfparse-users@li...
>>             Subject: [Perfparse-users] Warn values are not going into=20
>> database
>>                                     Hello, folks.
>>                         We have noticed today that perfparse is not=20
>> inserting the warning values into
>> perfdata_service_bin table, only the critical ones. So it"s impossible=
=20
>> to graph threshold
>> lines as warning values are always "0".
>>                         Does it happen because i"m not including all=20
>> fields of performance data on plugin
>> output? Is it neccessary to include all fields of performance values=20
>> on plugin output?
>>                         []"s
>>             Paulo Fessel
>>                   "This is not right. This is not even wrong."=20
>> (Wolfgang Pauli)        Paulo Fessel
>> Administrador de Ambiente e Sistemas UNIX     PrimeSys Solu=E7=F5es=20
>> Empresariais
>> Av. Brig. Faria Lima, 1485 - 13=B0 andar
>> Torre Norte - Pinheiros
>> 01451-904
>> S=E3o Paulo - SP     paulo.fessel@pr...     tel:
>> fax:
>> mobile:     +55 (11) 3038-6554
>> +55 (11) 3038-6508
>> +55 (11) 8259-0353         Signature powered by Plaxo=20
>> <http://www.plaxo.com/signature>      Want a signature like this?
>> <http://www.plaxo.com/signature>     Add me to your address book...
>> <https://www.plaxo.com/add_me?u=3D8590019246&v0=3D166225&k0=3D16011085=
62>    =20
>>          =20
>>
>>
>>
>> -------------------------------------------------------
>> This SF.net email is sponsored by: IT Product Guide on ITManagersJourn=
al
>> Use IT products in your business? Tell us what you think of them. Give=
 us
>> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out=
=20
>> more
>> http://productguide.itmanagersjournal.com/guidepromo.tmpl
>> _______________________________________________
>> Perfparse-users mailing list
>> Per...@li...
>> https://lists.sourceforge.net/lists/listinfo/perfparse-users
>=20
>=20
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJourna=
l
> Use IT products in your business? Tell us what you think of them. Give =
us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out =
more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> Perfparse-users mailing list
> Per...@li...
> https://lists.sourceforge.net/lists/listinfo/perfparse-users
>=20

[Perfparse-users] New version, 0.100.7

[Ben C. <Be...@cl...>]

New version 0.100.7 out.

This version does not contain Yves new parser, which I invite you to 
check out.  This will come soon.

This version has some of the options Jeff Scott requested.  The 'Saved 
Graph' options are not far more competent.  Jeff also asked for reports 
of multiple graphs.  This is a long term idea I have not had time to 
develop, but it will come soon.

There is now an option to permanently delete a host and all attached data.

There is also a fix to two big bugs.  My apologies to any users who 
experienced these.

1. New users might not have got *any* raw plugin output reporting to 
work.  This is fixed.

2. Deletion Policies for Binary data may have crashed.  This is also fixed.

Regards, Ben.

Re: [Perfparse-users] RE: RES: Warn values are not going into database

[Clif J. S. <per...@cj...>]

Never mind.  I was thinking the Warn/Crit lines would always be shown as=20
horizontal whether reached or not.  After testing, I see they only show=20
as part of the graph when reached.

cjs


Clif J. Smith wrote:

> I just installed v0.100.6 and I'm having the same issue.  I did tried=20
> the hack to no avail, although the settings were already updated, I=20
> just put them in the same order.  Any ideas?
>
> cjs
>
> From: Paulo Afonso Graner Fessel <paulo@pr...>
> RES: Warn values are not going into database  2004-08-13 13:15
>
> Ultra-quick hack that seems to solve my problem:
>
> In perfparse/perfparse.c:
>
> #define TPERFDATA_MIN   2
> #define TPERFDATA_MAX   3
> #define TPERFDATA_WARN  0
> #define TPERFDATA_CRIT  1
> #define TPERFDATA_VALUE 4
>
> instead of
>
> #define TPERFDATA_MIN   0
> #define TPERFDATA_MAX   1
> #define TPERFDATA_WARN  2
> #define TPERFDATA_CRIT  3
> #define TPERFDATA_VALUE 4
>
> The lines on the database now show
>
>
> +------------+---------------------+--------+---------------------+----=
-----+--------+----------+--------+=20
>
>  | host_name | service_description | metric | ctime               |=20
> value   | warn   |
> critical | state  |
>
> +------------+---------------------+--------+---------------------+----=
-----+--------+----------+--------+=20
>
>  | nagioslab | /dev/vg00/rootlv    | /      | 2004-08-13 09:58:11 |   =20
> 5211 |   8567 |    9575 |      0 |
>
> +------------+---------------------+--------+---------------------+----=
-----+--------+----------+--------+=20
>
>
> What, I think, should be the correct behavior.
>
> []"s
> Paulo
>
>
>       "This is not right. This is not even wrong." (Wolfgang Pauli)   =20
>     Paulo Fessel
> Administrador de Ambiente e Sistemas UNIX     PrimeSys Solu=E7=F5es=20
> Empresariais
> Av. Brig. Faria Lima, 1485 - 13=B0 andar
> Torre Norte - Pinheiros
> 01451-904
> S=E3o Paulo - SP     paulo.fessel@pr...     tel:
> fax:
> mobile:     +55 (11) 3038-6554
> +55 (11) 3038-6508
> +55 (11) 8259-0353         Signature powered by Plaxo=20
> <http://www.plaxo.com/signature>      Want a signature like this?
> <http://www.plaxo.com/signature>     Add me to your address book...
> <https://www.plaxo.com/add_me?u=3D8590019246&v0=3D166225&k0=3D160110856=
2>   =20
>
>
>   _____=20
>     De: Paulo Afonso Graner Fessel
>     Enviada em: sexta-feira, 13 de agosto de 2004 09:02
>     Para: Cook, Garry; perfparse-users@li...
>     Assunto: RES: [Perfparse-users] Warn values are not going into=20
> database
>             I wasn"t at the office today, so I"ll try to describe=20
> what"s happening.
>         Here"s for example one row of data took from=20
> perfdata_service_bin:
>   =20
>  =20
> +-----------+---------------------+--------+---------------------+-----=
----+--------+----------+--------+=20
>
>     | host_name | service_description | metric | ctime               |=20
> value   | warn   |
> critical | state  |
>
>  =20
> +-----------+---------------------+--------+---------------------+-----=
----+--------+----------+--------+=20
>
>     | nagioslab | /dev/vg00/rootlv    | /      | 2004-07-23 14:35:10=20
> |    4822 |      0 |   10079 |      0 |
>
>  =20
> +-----------+---------------------+--------+---------------------+-----=
----+--------+----------+--------+=20
>
>         On the other hand, take a look at the output of check_disk:
>         [root@nagioslab libexec]# ./check_disk -w 15% -c 5% -p /
>     DISK OK - free space: / 4869 MB (48%);| /=3D5211MB;8567;9575;0;1007=
9
>         The line recorded at serviceperf.log shows
>         1092398291      nagioslab       /dev/vg00/rootlv        DISK=20
> OK - free space: /
>     4869 MB (48%):  OK       /=3D5211MB;8567;9575;0;10079
>         Seems that the values that are making into the database are=20
> minimum (0) and maximum
> (10079) values instead of warning (10064) and critical (10074) ones.=20
> My patched check_nt
> (that provides also perfdata information) also provides evidence=20
> supporting this:
>         [root@nagioslab libexec]# ./check_nt -H 10.4.8.135 -v=20
> USEDDISKSPACE -l c -w 85% -c 95%
>     c:\ - total: 37.27 Gb - used: 7.31 Gb (20%) - free 29.96 Gb
> (80%)|c=3D7.310GB;31.678;35.404;;37.268
>         Now, the line recorded at the database:
>   =20
>  =20
> +------------+---------------------------+--------+--------------------=
-+---------+--------+----------+--------+=20
>
>     | host_name  | service_description       | metric |=20
> ctime               | value   | warn  | critical | state  |
>
>  =20
> +------------+---------------------------+--------+--------------------=
-+---------+--------+----------+--------+=20
>
>     | bradesk150 | Disco C:                  | c      | 2004-07-23=20
> 15:09:11 |   5.909 |      0
> |    37.26 |      0 |
>
>  =20
> +------------+---------------------------+--------+--------------------=
-+---------+--------+----------+--------+=20
>
>         Again, we see that warn =3D 0 and critical =3D- 37.26, when the=
=20
> correct information should
> have been warn =3D 31.68 and critical =3D 35.40. Also, as you can see,=20
> both plugins provide
> output in the format you mentioned - that is,=20
> "label"=3Dvalue[UOM];[warn];[crit];[min];[max].
>         TIA,
>         Paulo Fessel
>           "This is not right. This is not even wrong." (Wolfgang=20
> Pauli)        Paulo Fessel
> Administrador de Ambiente e Sistemas UNIX     PrimeSys Solu=E7=F5es=20
> Empresariais
> Av. Brig. Faria Lima, 1485 - 13=B0 andar
> Torre Norte - Pinheiros
> 01451-904
> S=E3o Paulo - SP     paulo.fessel@pr...     tel:
> fax:
> mobile:     +55 (11) 3038-6554
> +55 (11) 3038-6508
> +55 (11) 8259-0353         Signature powered by Plaxo=20
> <http://www.plaxo.com/signature>      Want a signature like this?
> <http://www.plaxo.com/signature>     Add me to your address book...
> <https://www.plaxo.com/add_me?u=3D8590019246&v0=3D166225&k0=3D160110856=
2>    =20
>   =20
>
>   _____=20
>         De: Cook, Garry [mailto:GWCOOK@ma...]
>         Enviada em: quinta-feira, 12 de agosto de 2004 12:07
>         Para: Paulo Afonso Graner Fessel; perfparse-users@li...
>         Assunto: RE: [Perfparse-users] Warn values are not going into=20
> database
>                         I"m not sure that I completely understand your=20
> question... What do you mean by "I"m not
> including all fields of performance data on plugin output"?
>                 Plugin output of performance data should be in the form=
at
> "label"=3Dvalue[UOM];[warn];[crit];[min];[max]
>         Please see=20
> http://nagiosplug.sourceforge.net/developer-guidelines.html#AEN185 for
> detailed information.
>                 As you can see from the above, some of the variables=20
> are optional (those enclosed in
> square brackets). If your performance data does not supply the warning=20
> and critical values,
> they will not make it into the database.
>
>         Garry W. Cook, CCNA
>         Network Infrastructure Manager
>         MACTEC, Inc. - http://www.mactec.com/
>         303.308.6228 (Office) - 720.220.1862 (Mobile)
>
>             -----Original Message-----
>             From: perfparse-users-admin@li...
> [mailto:perfparse-users-admin@li...] On Behalf Of Paulo Afonso Graner=20
> Fessel
>             Sent: Wednesday, August 11, 2004 2:44 PM
>             To: perfparse-users@li...
>             Subject: [Perfparse-users] Warn values are not going into=20
> database
>                                     Hello, folks.
>                         We have noticed today that perfparse is not=20
> inserting the warning values into
> perfdata_service_bin table, only the critical ones. So it"s impossible=20
> to graph threshold
> lines as warning values are always "0".
>                         Does it happen because i"m not including all=20
> fields of performance data on plugin
> output? Is it neccessary to include all fields of performance values=20
> on plugin output?
>                         []"s
>             Paulo Fessel
>                   "This is not right. This is not even wrong."=20
> (Wolfgang Pauli)        Paulo Fessel
> Administrador de Ambiente e Sistemas UNIX     PrimeSys Solu=E7=F5es=20
> Empresariais
> Av. Brig. Faria Lima, 1485 - 13=B0 andar
> Torre Norte - Pinheiros
> 01451-904
> S=E3o Paulo - SP     paulo.fessel@pr...     tel:
> fax:
> mobile:     +55 (11) 3038-6554
> +55 (11) 3038-6508
> +55 (11) 8259-0353         Signature powered by Plaxo=20
> <http://www.plaxo.com/signature>      Want a signature like this?
> <http://www.plaxo.com/signature>     Add me to your address book...
> <https://www.plaxo.com/add_me?u=3D8590019246&v0=3D166225&k0=3D160110856=
2>    =20
>           =20
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJourna=
l
> Use IT products in your business? Tell us what you think of them. Give =
us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out=20
> more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> Perfparse-users mailing list
> Per...@li...
> https://lists.sourceforge.net/lists/listinfo/perfparse-users

[Perfparse-users] RE: RES: Warn values are not going into database

[Clif J. S. <per...@cj...>]

I'm having the same problem.  I tried the hack below on a
newly installed v0.100.6 to no avail.  Although I noticed
the values were already the same, I just changed the order. =20

Any ideas?

cjs

From: Paulo Afonso Graner Fessel <paulo@pr...>
RES: Warn values are not going into database  =20
2004-08-13 13:15

Ultra-quick hack that seems to solve my problem:
 =20
 In perfparse/perfparse.c:
 =20
 #define TPERFDATA_MIN   2
 #define TPERFDATA_MAX   3
 #define TPERFDATA_WARN  0
 #define TPERFDATA_CRIT  1
 #define TPERFDATA_VALUE 4
=20
 instead of=20
 =20
 #define TPERFDATA_MIN   0
 #define TPERFDATA_MAX   1
 #define TPERFDATA_WARN  2
 #define TPERFDATA_CRIT  3
 #define TPERFDATA_VALUE 4
=20
 The lines on the database now show
 =20

+------------+---------------------+--------+---------------------+------=
---+--------+----------+--------+
  | host_name | service_description | metric | ctime               | valu=
e   | warn   |
critical | state  |

+------------+---------------------+--------+---------------------+------=
---+--------+----------+--------+
  | nagioslab | /dev/vg00/rootlv    | /      | 2004-08-13 09:58:11 |    5=
211 |   8567 |   =20
9575 |      0 |

+------------+---------------------+--------+---------------------+------=
---+--------+----------+--------+
=20
 What, I think, should be the correct behavior.
 =20
 []"s
 Paulo
 =20
 =20
  	 "This is not right. This is not even wrong." (Wolfgang Pauli)=09
 =09
 Paulo Fessel
 Administrador de Ambiente e Sistemas UNIX 	PrimeSys Solu=E7=F5es Empresa=
riais
 Av. Brig. Faria Lima, 1485 - 13=B0 andar
 Torre Norte - Pinheiros
 01451-904
 S=E3o Paulo - SP =09
 paulo.fessel@pr... 	tel:=20
 fax:=20
 mobile: 	+55 (11) 3038-6554
 +55 (11) 3038-6508
 +55 (11) 8259-0353 =09
 =09
 Signature powered by Plaxo <http://www.plaxo.com/signature> <http://www.=
plaxo.com/signature%3E> 	 Want a signature like this?
<http://www.plaxo.com/signature> <http://www.plaxo.com/signature%3E> =09
 Add me to your address book...
<https://www.plaxo.com/add_me?u=3D8590019246&v0=3D166225&k0=3D1601108562>=
 <https://www.plaxo.com/add_me?u=3D8590019246&v0=3D166225&k0=3D1601108562=
%3E> =09
 =20
=20
=20
   _____ =20
=20
 	De: Paulo Afonso Graner Fessel=20
 	Enviada em: sexta-feira, 13 de agosto de 2004 09:02
 	Para: Cook, Garry; perfparse-users@li...
 	Assunto: RES: [Perfparse-users] Warn values are not going into database
 =09
 =09
 	I wasn"t at the office today, so I"ll try to describe what"s happening.
 	=20
 	Here"s for example one row of data took from perfdata_service_bin:
 	=20

	+-----------+---------------------+--------+---------------------+------=
---+--------+----------+--------+
 	| host_name | service_description | metric | ctime               | valu=
e   | warn   |
critical | state  |

	+-----------+---------------------+--------+---------------------+------=
---+--------+----------+--------+
 	| nagioslab | /dev/vg00/rootlv    | /      | 2004-07-23 14:35:10 |    4=
822 |      0 |  =20
10079 |      0 |

	+-----------+---------------------+--------+---------------------+------=
---+--------+----------+--------+
 	=20
 	On the other hand, take a look at the output of check_disk:
 	=20
 	[root@nagioslab libexec]# ./check_disk -w 15% -c 5% -p /
 	DISK OK - free space: / 4869 MB (48%);| /=3D5211MB;8567;9575;0;10079
 	=20
 	The line recorded at serviceperf.log shows
 	=20
 	1092398291      nagioslab       /dev/vg00/rootlv        DISK OK - free =
space: /
 	4869 MB (48%):  OK       /=3D5211MB;8567;9575;0;10079
 =09
 	Seems that the values that are making into the database are minimum (0)=
 and maximum
(10079) values instead of warning (10064) and critical (10074) ones. My p=
atched check_nt
(that provides also perfdata information) also provides evidence supporti=
ng this:
 	=20
 	[root@nagioslab libexec]# ./check_nt -H 10.4.8.135 -v USEDDISKSPACE -l =
c -w 85% -c 95%
 	c:\ - total: 37.27 Gb - used: 7.31 Gb (20%) - free 29.96 Gb
(80%)|c=3D7.310GB;31.678;35.404;;37.268
 	=20
 	Now, the line recorded at the database:
 	=20

	+------------+---------------------------+--------+---------------------=
+---------+--------+----------+--------+
 	| host_name  | service_description       | metric | ctime              =
 | value   | warn =20
| critical | state  |

	+------------+---------------------------+--------+---------------------=
+---------+--------+----------+--------+
 	| bradesk150 | Disco C:                  | c      | 2004-07-23 15:09:11=
 |   5.909 |      0
|    37.26 |      0 |

	+------------+---------------------------+--------+---------------------=
+---------+--------+----------+--------+
 =09
 	Again, we see that warn =3D 0 and critical =3D- 37.26, when the correct=
 information should
have been warn =3D 31.68 and critical =3D 35.40. Also, as you can see, bo=
th plugins provide
output in the format you mentioned - that is, "label"=3Dvalue[UOM];[warn]=
;[crit];[min];[max].
 	=20
 	TIA,
 	=20
 	Paulo Fessel
 	=20
  	 "This is not right. This is not even wrong." (Wolfgang Pauli)=09
 =09
 Paulo Fessel
 Administrador de Ambiente e Sistemas UNIX 	PrimeSys Solu=E7=F5es Empresa=
riais
 Av. Brig. Faria Lima, 1485 - 13=B0 andar
 Torre Norte - Pinheiros
 01451-904
 S=E3o Paulo - SP =09
 paulo.fessel@pr... 	tel:=20
 fax:=20
 mobile: 	+55 (11) 3038-6554
 +55 (11) 3038-6508
 +55 (11) 8259-0353 =09
 =09
 Signature powered by Plaxo <http://www.plaxo.com/signature> <http://www.=
plaxo.com/signature%3E> 	 Want a signature like this?
<http://www.plaxo.com/signature> <http://www.plaxo.com/signature%3E> =09
 Add me to your address book...
<https://www.plaxo.com/add_me?u=3D8590019246&v0=3D166225&k0=3D1601108562>=
 <https://www.plaxo.com/add_me?u=3D8590019246&v0=3D166225&k0=3D1601108562=
%3E> =09
 	=20
=20
=20
   _____ =20
=20
 		De: Cook, Garry [mailto:GWCOOK@ma...]=20
 		Enviada em: quinta-feira, 12 de agosto de 2004 12:07
 		Para: Paulo Afonso Graner Fessel; perfparse-users@li...
 		Assunto: RE: [Perfparse-users] Warn values are not going into database
 	=09
 	=09
 		I"m not sure that I completely understand your question... What do you=
 mean by "I"m not
including all fields of performance data on plugin output"?
 		=20
 		Plugin output of performance data should be in the format
"label"=3Dvalue[UOM];[warn];[crit];[min];[max]
 		Please see http://nagiosplug.sourceforge.net/developer-guidelines.html=
#AEN185 for
detailed information.
 		=20
 		As you can see from the above, some of the variables are optional (tho=
se enclosed in
square brackets). If your performance data does not supply the warning an=
d critical values,
they will not make it into the database.
=20
 		Garry W. Cook, CCNA
 		Network Infrastructure Manager
 		MACTEC, Inc. - http://www.mactec.com/
 		303.308.6228 (Office) - 720.220.1862 (Mobile)=20
=20
 			-----Original Message-----
 			From: perfparse-users-admin@li...
[mailto:perfparse-users-admin@li...] On Behalf Of Paulo Afonso Graner Fes=
sel
 			Sent: Wednesday, August 11, 2004 2:44 PM
 			To: perfparse-users@li...
 			Subject: [Perfparse-users] Warn values are not going into database
 		=09
 		=09
 			Hello, folks.
 			=20
 			We have noticed today that perfparse is not inserting the warning val=
ues into
perfdata_service_bin table, only the critical ones. So it"s impossible to=
 graph threshold
lines as warning values are always "0".
 			=20
 			Does it happen because i"m not including all fields of performance da=
ta on plugin
output? Is it neccessary to include all fields of performance values on p=
lugin output?
 			=20
 			[]"s
 			Paulo Fessel
 			=20
  	 "This is not right. This is not even wrong." (Wolfgang Pauli)=09
 =09
 Paulo Fessel
 Administrador de Ambiente e Sistemas UNIX 	PrimeSys Solu=E7=F5es Empresa=
riais
 Av. Brig. Faria Lima, 1485 - 13=B0 andar
 Torre Norte - Pinheiros
 01451-904
 S=E3o Paulo - SP =09
 paulo.fessel@pr... 	tel:=20
 fax:=20
 mobile: 	+55 (11) 3038-6554
 +55 (11) 3038-6508
 +55 (11) 8259-0353 =09
 =09
 Signature powered by Plaxo <http://www.plaxo.com/signature> <http://www.=
plaxo.com/signature%3E> 	 Want a signature like this?
<http://www.plaxo.com/signature> <http://www.plaxo.com/signature%3E> =09
 Add me to your address book...
<https://www.plaxo.com/add_me?u=3D8590019246&v0=3D166225&k0=3D1601108562>=
 <https://www.plaxo.com/add_me?u=3D8590019246&v0=3D166225&k0=3D1601108562=
%3E> =09