Menu
▾
▴
Re: [Perfparse-users] RE: RES: Warn values are not going into database
|
From: Ben C. <Be...@cl...> - 2004-10-04 13:00:13
|
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 |
