RE: [Perfparse-users] Problems with MySQL and documentations

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

Any check output should look like this:
check_nt -H 172.21.7.2 -p 1248 -v CPULOAD -l 70,40,80
CPU Load 0% (70 min average) |   '70 min avg Load'=3D0%;40;80;0;100

There should be a pipe at the end, it's the information after | that is =
to be sent to perfparse. Are you sure you have downloaded and installed =
all beta plugins? You need them to support performance data.

There is a better plugin than check_ping which is called check_icmp. =
We've had alot of discussions regarding check_icmp vs check_ping on the =
nagios users maillist.

If you could send me a copy of your conclusion that would be wonderful, =
I have had some of your problems but haven't been able to resolve all of =
them yet.

Thanks in advance!

----------------------------------------------
Sebastian Bergstroem
Technical coordinator
Kunskapsskolan i Sverige AB
seb...@ku...
-----------------------------------------------=20

> -----Original Message-----
> From: Jessica Holle [mailto:Je...@gm...]=20
> Sent: den 18 februari 2005 11:05
> To: per...@li...
> Subject: [Perfparse-users] Problems with MySQL and documentations
>=20
> I have some more problem, or only one... we will see and I=20
> hope aou answer quick... :-)
>=20
>=20
> My SQL database work fine now :-)
> I can say I'm be proud of myself
>=20
> But now I have a problems with the bin data...=20
>=20
> My database looks so:
>=20
> mysql> select * from
> perfdata_service_raw;
> +----+-----------+---------------------+---------------------+
> -------------------------------------------+---------------+
> | id | host_name | service_description | ctime              =20
> | txt_data    =20
>                             | nagios_status
> |
> +----+-----------+---------------------+---------------------+
> -------------------------------------------+---------------+
> |  1 | jholle    | Ping                | 2005-02-18 10:23:37=20
> | PING OK -
> Packet loss =3D 0%, RTA =3D 0.33 ms |             0 |
> |  2 | jholle    | Ping                | 2005-02-18 10:24:37=20
> | PING OK -
> Packet loss =3D 0%, RTA =3D 0.29 ms |             0 |
> |  3 | jholle    | Ping                | 2005-02-18 10:25:37=20
> | PING OK -
> Packet loss =3D 0%, RTA =3D 0.33 ms |             0 |
> |  4 | jholle    | Ping                | 2005-02-18 10:26:37=20
> | PING OK -
> Packet loss =3D 0%, RTA =3D 0.33 ms |             0 |
> |  5 | jholle    | Ping                | 2005-02-18 10:27:37=20
> | PING OK -
> Packet loss =3D 0%, RTA =3D 0.34 ms |             0 |
> |  6 | jholle    | Ping                | 2005-02-18 10:28:37=20
> | PING OK -
> Packet loss =3D 0%, RTA =3D 0.35 ms |             0 |
> |  7 | jholle    | Ping                | 2005-02-18 10:29:37=20
> | PING OK -
> Packet loss =3D 0%, RTA =3D 0.38 ms |             0 |
> |  8 | jholle    | Ping                | 2005-02-18 10:30:37=20
> | PING OK -
> Packet loss =3D 0%, RTA =3D 0.31 ms |             0 |
> |  9 | jholle    | Ping                | 2005-02-18 10:31:37=20
> | PING OK -
> Packet loss =3D 0%, RTA =3D 0.33 ms |             0 |
> | 10 | jholle    | Ping                | 2005-02-18 10:32:37=20
> | PING OK -
> Packet loss =3D 0%, RTA =3D 0.33 ms |             0 |
> | 11 | jholle    | Ping                | 2005-02-18 10:33:37=20
> | PING OK -
> Packet loss =3D 0%, RTA =3D 0.29 ms |             0 |
> | 12 | jholle    | Ping                | 2005-02-18 10:46:15=20
> | PING OK -
> Packet loss =3D 0%, RTA =3D 0.30 ms |             0 |
> | 13 | jholle    | Ping                | 2005-02-18 10:48:03=20
> | PING OK -
> Packet loss =3D 0%, RTA =3D 0.30 ms |             0 |
> | 14 | jholle    | Ping                | 2005-02-18 10:49:03=20
> | PING OK -
> Packet loss =3D 0%, RTA =3D 0.34 ms |             0 |
> | 15 | jholle    | Ping                | 2005-02-18 10:50:03=20
> | PING OK -
> Packet loss =3D 0%, RTA =3D 0.31 ms |             0 |
> | 16 | jholle    | Ping                | 2005-02-18 10:51:03=20
> | PING OK -
> Packet loss =3D 0%, RTA =3D 0.29 ms |             0 |
> | 17 | jholle    | Ping                | 2005-02-18 10:52:03=20
> | PING OK -
> Packet loss =3D 0%, RTA =3D 0.33 ms |             0 |
> | 18 | jholle    | Ping                | 2005-02-18 10:53:03=20
> | PING OK -
> Packet loss =3D 0%, RTA =3D 0.50 ms |             0 |
> | 19 | jholle    | Ping                | 2005-02-18 10:54:03=20
> | PING OK -
> Packet loss =3D 0%, RTA =3D 0.43 ms |             0 |
> | 20 | jholle    | Ping                | 2005-02-18 10:55:03=20
> | PING OK -
> Packet loss =3D 0%, RTA =3D 0.34 ms |             0
> |
> +----+-----------+---------------------+---------------------+
> -------------------------------------------+---------------+
> 20 rows in set (0.00 sec)
>=20
> mysql> select * from perfdata_service_bin;
> Empty set (0.00 sec)
>=20
>=20
> I the raw data section is all of the right data but in the=20
> bin data section is no data. I thing that no graphs can be=20
> established because of this.=20
>=20
> I've read the information from Yve about this site:
>=20
> http://wiki.perfparse.org/tiki-view_faq.php?faqId=3D6#q7
>=20
> And I tested my plugin on the command mode:
>=20
> nagios@rzvlabwks:/usr/local/nagor/nagios/libexec> ./check_ping -H
> 172.16.1.114 -w 100.0,20% -c 500.0,60%
> PING OK - Packet loss =3D 0%, RTA =3D 0.32 ms
>=20
>=20
> And this doesn't look like the right output.
>=20
> # PROCESS PERFORMANCE DATA OPTION
> # This determines whether or not Nagios will process=20
> performance # data returned from service and host checks.  If=20
> this option is # enabled, host performance data will be=20
> processed using the # host_perfdata_command (defined below)=20
> and service performance # data will be processed using the=20
> service_perfdata_command (also # defined below).  Read the=20
> HTML docs for more information on # performance data.
> # Values: 1 =3D process performance data, 0 =3D do not process=20
> performance data
>=20
> process_performance_data=3D1
>=20
>=20
>=20
> # HOST AND SERVICE PERFORMANCE DATA PROCESSING COMMANDS #=20
> These commands are run after every host and service check is=20
> # performed.  These commands are executed only if the #=20
> enable_performance_data option (above) is set to 1.  The=20
> command # argument is the short name of a command definition=20
> that you # define in your host configuration file.  Read the=20
> HTML docs for # more information on performance data.
>=20
> host_perfdata_command=3Dprocess-host-perfdata
> service_perfdata_command=3Dprocess-service-perfdata
>=20
>=20
> This is in my nagios.cfg set.=20
>=20
> And my nagios web interface says:
> Performance Data Being Processed?	Yes
>=20
>=20
> But I don't know how I get the bin data...
>=20
> Please help me....
>=20
> PS to Ben or Yves: After it all works here I write a=20
> conclusion and in which way I've done this. Should I mail=20
> this to you? I can mail it to you in german and in my broken=20
> english... :-)
>=20
> --
> DSL Komplett von GMX +++ Superg=FCnstig und stressfrei einsteigen!
> AKTION "Kein Einrichtungspreis" nutzen: http://www.gmx.net/de/go/dsl
>=20
>=20
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from=20
> real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=3D6595&alloc_id=3D14396&op=3Dclick
> _______________________________________________
> Perfparse-users mailing list
> Per...@li...
> https://lists.sourceforge.net/lists/listinfo/perfparse-users
>=20
>=20