[hobbit] Collecting RRD from custom script, but no graph

3 Mar 2006


      Thanks, this was the problem!
S
-----Original Message-----
From: Dan Vande More [mailto:bigdan at gmail.com]
Sent: 3-Mar-06 12:53 PM
To: hobbit at hswn.dk
Subject: Re: [hobbit] Collecting RRD from custom script, but no graph
Usually the magnifying glass link with no graph is a sign that the RRD
was unable to generate. This is normally because of a configuration
issue, and I seem to get them when my hobbitgraph.cfg section is
wrong.
I get the impression that your DEF line is incorrect in your
hobbitgraph.cfg file.
by using DEF:tr=trackoswex.rrd:tracks:AVERAGE, you are telling the
grapher to use the trackoswex.rrd file and "tracks" as the name of
your datasource. Is your datasource's name really "tracks"?
To find the name of your real datasource from a simple rrd file, do this:
rrdtool dump /path/to/your.rdd | less
Then search for the <RENAMED_ds> tag. (Should be right near the top.) For
instance, one of mine says:
    &lt;RENAMED_ds>
            &lt;RENAMED_name> procATemp &lt;/RENAMED_name>
            &lt;RENAMED_type> GAUGE &lt;/RENAMED_type>
            &lt;RENAMED_minimal_heartbeat> 600 &lt;/RENAMED_minimal_heartbeat>
            &lt;RENAMED_min> 0.0000000000e+00 &lt;/RENAMED_min>
            &lt;RENAMED_max> NaN &lt;/RENAMED_max>

            &lt;!-- PDP Status -->
            &lt;RENAMED_last_ds> UNKN &lt;/RENAMED_last_ds>
            &lt;RENAMED_value> 6.4550000000e+03 &lt;/RENAMED_value>
            &lt;RENAMED_unknown_sec> 0 &lt;/RENAMED_unknown_sec>
    &lt;/RENAMED_ds>
So my datasource's name is procATemp. Note that this only works for a
simple .rrd file. Some rrds contain several data sources, so don't let
this mislead you.
HTH,
Dan
On 3/3/06, Syms.MS at forces.gc.ca <Syms.MS at forces.gc.ca> wrote:
...
Hi, folks-
I wrote a custom data collection script to send varying data to hobbit- hobbit receives it ok, displays the status properly and populates an rrd to store the data, but then doesn't graph it.  I do get the graph name in a text hyperlink beside the magnifying glass icon, but that's it.
I've done a similar thing with hobbit on a debian box before without a problem, but now that I'm running it on an aging Redhat Advanced Server 3 box, it's giving me some trouble.
The configuration bits: I'm running rrdtool 1.0.48, gcc 2.3.3 and Hobbit 4.1.2p1.
The output line from my script:
${BB} ${BBDISP} "status ${MACHINE}.trackoswex ${COLOR} date
trackoswex: ${TRACKS}
"
In hobbitlaunch.cfg, I'ved added
[trackoswex]
ENVFILE /usr/local/hobbit/client/etc/hobbitclient.cfg
NEEDS hobbitd
CMD /usr/local/hobbit/server/ext/gccs/trackoswex.sh
LOGFILE $BBSERVERLOGS/hobbitclient.log
INTERVAL 30m
From hobbitgraph.cfg
[trackoswex]
TITLE OSWEX Tracks
YAXIS Number of tracks
DEF:tr=trackoswex.rrd:tracks:AVERAGE
AREA:tr#00CCCC:Tracks
COMMENT:These are the number of tracks received in the last 120 minutes.\n
GPRINT:tr:LAST: \: %5.1lf (cur)
GPRINT:tr:MAX: \: %5.1lf (max)
GPRINT:tr:MIN: \: %5.1lf (min)
GPRINT:tr:AVERAGE: \: %5.1lf (avg)\n
From hobbitserver.cfg
TEST2RRD="cpu=la,disk,inode,qtree,memory,$PINGCOLUMN=tcp,http=tcp,dns=tcp,dig=tcp,time=ntpstat,vmstat,iostat,netstat,temperature,apache,bind,sendmail,mailq,nmailq=mailq,socks,bea,iishealth,citrix,bbgen,bbtest,bbproxy,hobbitd,trackoswex=ncv"
This defines which RRD files to include on the "trends" column webpage,
and the order in which they appear.
GRAPHS="la,disk,inode,qtree,memory,users,vmstat,iostat,tcp.http,tcp,netstat,mrtg::1,temperature,ntpstat,apache,bind,sendmail,mailq,socks,bea,iishealth,citrix,bbgen,bbtest,bbproxy,hobbitd,trackoswex"
NCV_trackoswex="trackoswex:GAUGE"
Any help would be appreciated!
tks
S
To unsubscribe from the hobbit list, send an e-mail to
hobbit-unsubscribe at hswn.dk
To unsubscribe from the hobbit list, send an e-mail to
hobbit-unsubscribe at hswn.dk

[hobbit] Collecting RRD from custom script, but no graph

Syms.MS＠forces.gc.ca

This defines which RRD files to include on the "trends" column webpage,

and the order in which they appear.