This is something that would be outstanding for the wiki.
The MySQL stuff is actually already in my hobbtgraph file which initially puzzled me. After working through it a number of times, I was able to finally get it to work, but not without some difficulty.
Excellent work, Nelson.
--j
On Mar 27, 2010, at 5:44 AM, amaral8011 at googlemail.com wrote:
Ehehe
Once again sorry for the spaming.
I got the graphs working for mysql, I will be posting all the steps in this thread later for everyone that has the same problem in the future.
Regards
Nelson Sent from my BlackBerry® wireless device
From: Jerald Sheets <questy at gmail.com> Date: Fri, 26 Mar 2010 12:05:23 -0400 To: <hobbit at hswn.dk> Subject: Re: [hobbit] Mysql Graphing
Methinks Nelson's mail server is burping...
--j
On Mar 26, 2010, at 8:59 AM, Nelson Amaral wrote:
Hi
I have used a mysql script from xymonton to collect data into xymon, i get the data in xymon OK but the problem is the graphs right now.
The graphs come up in the page but is not plotting, the problem is some where between hobbitserver.cfg and hobbitgraph.cfg
I am asking for help while i carry on looking for the answer (maybe i'm missing something in the configuration)
please note that the rrd file is created in the data folder
I get the data in xymon example:
Fri Mar 26 14:54:26 2010 MySQL Server OK
threads: 1 questions: 990691 slow queries: 0 opens: 7128 flush tables: 1 open tables: 64 queries per second avg: 0.402 maxcon: 100
Server version: 5.0.77 Source distribution Uptime: 28 days 12 hours 19 min 1 sec
Server reports timestamp of 2010-03-26 14:54:26
and have added the following in hobbitserver.cfg in TEST2RRD i added mysql=ncv and then added the following line NCV_mysql="threads:GAUGE,questions:GAUGE,slow queries:GAUGE,opens:GAUGE,flush tables:GAUGE,open tables:GAUGE,queries per second avg:GAUGE" also in hobbitgraph.cfg i added the following (i only have the first 2 instances of data for testing purposes)
[mysql] TITLE mysql info YAXIS # DEF:threads=mysql.rrd:threads:AVERAGE
DEF:questions=mysql.rrd:questions:AVERAGE LINE1:threads#00CCCC:threads LINE2:questions#FF0000:questions COMMENT:\n GPRINT:threads:LAST:Threads \: %5.1lf (cur) GPRINT:threads:MAX: \: %5.1lf (max) GPRINT:threads:MIN: \: %5.1lf (min) GPRINT:threads:AVERAGE: \: %5.1lf (avg)\n GPRINT:questions:LAST:Questions\: %5.1lf%s (cur) GPRINT:questions:MAX: \: %5.1lf%s (max) GPRINT:questions:MIN: \: %5.1lf%s (min) GPRINT:questions:AVERAGE: \: %5.1lf%s (avg)\nRegards
Nelson Amaral
----- Original Message ----- From: "thorsten erdmann" <thorsten.erdmann at daimler.com> To: hobbit at hswn.dk Sent: Friday, 26 March, 2010 11:27:32 AM Subject: [hobbit] message filter and the DEFAULT section
Hi
I want to filter some messages from a specific server's message log. So I built a special rule in hobbit-clients.cfg to filter that message, but it is ignored. It seems Hobbit preferres the DEFAULT section. If I uncomment the DEFAULT LOG rule my special rule is used and the message is filtered.
So how can I have a default rule including some IGNORE clauses which is used for all my servers and an additional set of rule specific to one or more servers.
Here is my hobbit-client.cfg. The rule I currently playing with is marked with (***), it's the host s068c326. If I comment out the last two lines it works, if not the message "ntpd error" is detected as error.
HOST=s068310i DISK %^/platform.* IGNORE
HOST=s068310b DISK %^/platform.* IGNORE
HOST=s068a300 LOG %.* %(fatal|error) COLOR=red IGNORE=%(smb_proc_readdir_long|peer) LOG %.* warning COLOR=yellow
DISK * 10 15
HOST=s068c327 DISK /mnt IGNORE
#HOST=%s068c32.* HOST=s068c326 #HOST=s068c320,s068c321,s068c322,s068c323,s068c324,s068c325,s068c326,s068c327 LOG %.* %(fatal|error) IGNORE=%ntpd COLOR=red #(***)
HOST=s068c320,s068c321,s068c322 PROC "lmgrd -c" 1 1 PROC "pam_lmd" 1 1
DEFAULT # These are the built-in defaults. UP 1h LOAD 5.0 10.0 DISK * 90 95 DISK /media/cdrom 101 101 MEMPHYS 100 101 MEMSWAP 50 80 MEMACT 90 97
LOG %.* %(fatal|error) COLOR=red IGNORE=%(read_socket_data|peer) LOG %.* warning COLOR=yellow IGNORE=40960Thank you for help
Thorsten Erdmann
If you are not the intended addressee, please inform us immediately that you have received this e-mail in error, and delete it. We thank you for your cooperation.