Xymon Mailing List Archive search

custom rrd data graph

10 messages in this thread

list Shifter · Tue, 7 Nov 2006 16:58:13 -0800 ·
Hi all,

I've spent a good deal of time today perusing the archives and man pages
hoping to glean the answers to my problem of creating a custom rrd data (not
status) graph.  The process should be similar but darn near everything I've
seen deals with status graphs.

Here's the contents of my ext script on the client:

(stuff to put a value into /tmp/pcpu.txt)
$BB $BBDISP "data $MACHINE.pcpu
`cat /tmp/pcpu.txt`"


The contents of /tmp/pcpu.txt:
pcpu_idle : 97.16

On the server side of things I've modified the hobbitserver.cfg files'
TEST2RRD and GRAPHS lines to append "pcpu_idle=ncv".
I also have this line in the same file: NCV_pcpu_idle="pcpu_idle:GAUGE"

hobbitgraph.cfg also includes this definition:
[pcpu]
        TITLE ESX CPU Utilitization
        YAXIS % Used
        -u 100
        -r
        DEF:cpu_idl=pcpu.rrd:cpu_idl:AVERAGE
        CDEF:pbusy=100,cpu_idl,-
        LINE2:pbusy#00CC00:% CPU busy
        GPRINT:pbusy:LAST: \: %5.1lf (cur)
        GPRINT:pbusy:MAX: \: %5.1lf (max)
        GPRINT:pbusy:MIN: \: %5.1lf (min)
        GPRINT:pbusy:AVERAGE: \: %5.1lf (avg)\n

I don't have a pcpu.rrd file in the rrd/host directory which I would expect
to see.  I don't see any error messages in the client logs about not being
able to communicate.  Am I missing something obvious?  Any help would be
appreciated, thanks.

Sage
list Al Jeffcoat · Tue, 7 Nov 2006 21:11:25 -0500 ·
I just went through a very similar situation in the last 4 days.  Some
things with underscores worked, some things didn't.  There was a
suggestion to put spaces between the DS and VALUE, which also had mixed
results.

 
The final fix was to remove underscores from everything, and that solved
my problem across the board.  My users would have rather had the
underscores due to some naming similarities, however, they are living
with it to get the graphs :-).  Funny how much power a graph has.

 
Al
quoted from Shifter

 
From: Shifter [mailto:user-312408c55c39@xymon.invalid] 
Sent: Tuesday, November 07, 2006 7:58 PM
To: user-ae9b8668bcde@xymon.invalid
Subject: [hobbit] custom rrd data graph

 
Hi all,

I've spent a good deal of time today perusing the archives and man pages
hoping to glean the answers to my problem of creating a custom rrd data
(not status) graph.  The process should be similar but darn near
everything I've seen deals with status graphs. 

Here's the contents of my ext script on the client:

(stuff to put a value into /tmp/pcpu.txt)
$BB $BBDISP "data $MACHINE.pcpu
`cat /tmp/pcpu.txt`"


The contents of /tmp/pcpu.txt: 

pcpu_idle : 97.16


On the server side of things I've modified the hobbitserver.cfg files'
TEST2RRD and GRAPHS lines to append "pcpu_idle=ncv". 
I also have this line in the same file: NCV_pcpu_idle="pcpu_idle:GAUGE"

hobbitgraph.cfg also includes this definition:
[pcpu]
        TITLE ESX CPU Utilitization
        YAXIS % Used
        -u 100 
        -r
        DEF:cpu_idl=pcpu.rrd:cpu_idl:AVERAGE
        CDEF:pbusy=100,cpu_idl,-
        LINE2:pbusy#00CC00:% CPU busy
        GPRINT:pbusy:LAST: \: %5.1lf (cur)
        GPRINT:pbusy:MAX: \: %5.1lf (max) 
        GPRINT:pbusy:MIN: \: %5.1lf (min)
        GPRINT:pbusy:AVERAGE: \: %5.1lf (avg)\n

I don't have a pcpu.rrd file in the rrd/host directory which I would
expect to see.  I don't see any error messages in the client logs about
not being able to communicate.  Am I missing something obvious?  Any
help would be appreciated, thanks. 

Sage


This e-mail message and any attached files are confidential and are intended solely for the use of the addressee(s) named above. If you are not the intended recipient, any review, use, or distribution of this e-mail message and any attached files is strictly prohibited. This communication may contain material protected by Federal privacy regulations, attorney-client work product, or other privileges. If you have received this confidential communication in error, please notify the sender immediately by reply e-mail message and permanently delete the original message.  To reply to our email administrator directly, send an email to:  user-ecde3bbc361d@xymon.invalid .  If this e-mail message concerns a contract matter, be advised that no employee or agent is authorized to conclude any binding agreement on behalf of Orlando Regional Healthcare by e-mail without express written confirmation by an officer of the corporation. Any views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of Orlando Regional Healthcare.
list Shifter · Wed, 8 Nov 2006 09:58:38 -0800 ·
Well, I tried replacing all instances of pcpu_idle with pcpuIdle, restarted
server and client but still no rrd's.  Is there some way I can check to see
that the data is actually reaching the server?  I'm getting data and graphs
for load average, disk, memory utilization, etc.  The stuff that usually
shows up in trends, so I know the client can reach the host.

Sage
quoted from Al Jeffcoat

On 11/7/06, Jeffcoat, Al <user-eca780a472ed@xymon.invalid> wrote:
 I just went through a very similar situation in the last 4 days.  Some
things with underscores worked, some things didn't.  There was a suggestion
to put spaces between the DS and VALUE, which also had mixed results.


The final fix was to remove underscores from everything, and that solved
my problem across the board.  My users would have rather had the underscores
due to some naming similarities, however, they are living with it to get the

graphs J.  Funny how much power a graph has.
quoted from Al Jeffcoat


Al


*From:* Shifter [mailto:user-312408c55c39@xymon.invalid]
*Sent:* Tuesday, November 07, 2006 7:58 PM
*To:* user-ae9b8668bcde@xymon.invalid
*Subject:* [hobbit] custom rrd data graph


Hi all,

I've spent a good deal of time today perusing the archives and man pages
hoping to glean the answers to my problem of creating a custom rrd data (not
status) graph.  The process should be similar but darn near everything I've
seen deals with status graphs.

Here's the contents of my ext script on the client:

(stuff to put a value into /tmp/pcpu.txt)
$BB $BBDISP "data $MACHINE.pcpu
`cat /tmp/pcpu.txt`"


The contents of /tmp/pcpu.txt:

pcpu_idle : 97.16


On the server side of things I've modified the hobbitserver.cfg files'
TEST2RRD and GRAPHS lines to append "pcpu_idle=ncv".
I also have this line in the same file: NCV_pcpu_idle="pcpu_idle:GAUGE"

hobbitgraph.cfg also includes this definition:
[pcpu]
        TITLE ESX CPU Utilitization
        YAXIS % Used
        -u 100
        -r
        DEF:cpu_idl=pcpu.rrd:cpu_idl:AVERAGE
        CDEF:pbusy=100,cpu_idl,-
        LINE2:pbusy#00CC00:% CPU busy
        GPRINT:pbusy:LAST: \: %5.1lf (cur)
        GPRINT:pbusy:MAX: \: %5.1lf (max)
        GPRINT:pbusy:MIN: \: %5.1lf (min)
        GPRINT:pbusy:AVERAGE: \: %5.1lf (avg)\n

I don't have a pcpu.rrd file in the rrd/host directory which I would
expect to see.  I don't see any error messages in the client logs about not
being able to communicate.  Am I missing something obvious?  Any help would
be appreciated, thanks.

Sage

This e-mail message and any attached files are confidential and are
intended solely for the use of the addressee(s) named above. If you are not
the intended recipient, any review, use, or distribution of this e-mail
message and any attached files is strictly prohibited. This communication
may contain material protected by Federal privacy regulations,
attorney-client work product, or other privileges. If you have received this
confidential communication in error, please notify the sender immediately by
reply e-mail message and permanently delete the original message. To reply
to our email administrator directly, send an email to:
user-ecde3bbc361d@xymon.invalid . If this e-mail message concerns a
contract matter, be advised that no employee or agent is authorized to
conclude any binding agreement on behalf of Orlando Regional Healthcare by
e-mail without express written confirmation by an officer of the
corporation. Any views or opinions presented in this e-mail are solely those
of the author and do not necessarily represent those of Orlando Regional
Healthcare.
list Charles Goyard · Wed, 8 Nov 2006 19:05:44 +0100 ·
Hi,
quoted from Shifter
$BB $BBDISP "data $MACHINE.pcpu
`cat /tmp/pcpu.txt`"


The contents of /tmp/pcpu.txt:
pcpu_idle : 97.16

On the server side of things I've modified the hobbitserver.cfg files'
TEST2RRD and GRAPHS lines to append "pcpu_idle=ncv".
I also have this line in the same file: NCV_pcpu_idle="pcpu_idle:GAUGE"
The problem comes from that your setup should read as :

TEST2RRD="$TEST2RRD,pcpu=ncv"
                    ^-- match the name of the status
NCV_pcpu="pcpu_idle:GAUGE"
    ^-- same thing here


Regards,

-- 
Charles Goyard - user-98f9625a7a59@xymon.invalid - (+33) 1 45 38 01 31
list Shifter · Wed, 8 Nov 2006 10:40:23 -0800 ·
I don't quite follow Charles.  Here's the relevant lines from my
hobbitserver.cfg file:

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,files,procs=processes,ports,clock,lines,pcpuIdle=ncv"

GRAPHS="la,disk,inode,qtree,files,processes,memory,users,vmstat,iostat,
tcp.http
,tcp,ncv,netstat,ifstat,mrtg::1,ports,temperature,ntpstat,apache,bind,sendmail,mailq,socks,bea,iishealth,citrix,bbgen,bbtest,bbproxy,hobbitd,clock,lines,pcpuIdle=ncv"

NCV_pcpuIdle="pcpuIdle:GAUGE"

The message I'm sending from the client is a data message, not a status
message.  This is what's coming from my client via an ext script running
every 5 minutes:

$BB $BBDISP "data $MACHINE.pcpu
`cat /tmp/pcpu.txt`
"
Sage
quoted from Charles Goyard

On 11/8/06, Charles Goyard <user-98f9625a7a59@xymon.invalid> wrote:
On the server side of things I've modified the hobbitserver.cfg files'
TEST2RRD and GRAPHS lines to append "pcpu_idle=ncv".
I also have this line in the same file: NCV_pcpu_idle="pcpu_idle:GAUGE"
The problem comes from that your setup should read as :

TEST2RRD="$TEST2RRD,pcpu=ncv"
                    ^-- match the name of the status
NCV_pcpu="pcpu_idle:GAUGE"
    ^-- same thing here


Regards,

--

list Charles Jones · Wed, 08 Nov 2006 12:00:25 -0700 ·
Your GRAPHS setting should not have =ncv, only TEST2RRD should.  In other words, it should be like this:
GRAPHS="la,disk,inode,qtree,files,processes,memory,users,vmstat,iostat,tcp.http,tcp,ncv,netstat,ifstat,mrtg::1,ports,temperature,ntpstat,apache,bind,sendmail,mailq,socks,bea,iishealth,citrix,bbgen,bbtest,bbproxy,hobbitd,clock,lines,pcpuIdle"

The rest looks fine. Of course make sure you define a [pcpuIdle] section in hobbitgraph.cfg as well. I believe you also have to restart Hobbit after any changes to hobbitserver.cfg.

-Charles
quoted from Shifter

Shifter wrote:
I don't quite follow Charles.  Here's the relevant lines from my hobbitserver.cfg file:

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,files,procs=processes,ports,clock,lines,pcpuIdle=ncv" 

GRAPHS="la,disk,inode,qtree,files,processes,memory,users,vmstat,iostat,tcp.http,tcp,ncv,netstat,ifstat,mrtg::1,ports,temperature,ntpstat,apache,bind,sendmail,mailq,socks,bea,iishealth,citrix,bbgen,bbtest,bbproxy,hobbitd,clock,lines,pcpuIdle=ncv" 
quoted from Shifter

NCV_pcpuIdle="pcpuIdle:GAUGE"

The message I'm sending from the client is a data message, not a status message.  This is what's coming from my client via an ext script running every 5 minutes:

$BB $BBDISP "data $MACHINE.pcpu
`cat /tmp/pcpu.txt`
"
Sage

On 11/8/06, *Charles Goyard* <user-98f9625a7a59@xymon.invalid <mailto:user-98f9625a7a59@xymon.invalid>> wrote:
On the server side of things I've modified the hobbitserver.cfg
    files'
TEST2RRD and GRAPHS lines to append "pcpu_idle=ncv".
I also have this line in the same file:
    NCV_pcpu_idle="pcpu_idle:GAUGE"

    The problem comes from that your setup should read as :

    TEST2RRD="$TEST2RRD,pcpu=ncv"
                        ^-- match the name of the status
    NCV_pcpu="pcpu_idle:GAUGE"
        ^-- same thing here


    Regards,

    --

list Charles Goyard · Wed, 8 Nov 2006 20:17:02 +0100 ·
Hi,

Shifter wrote :
$BB $BBDISP "data $MACHINE.pcpu
`cat /tmp/pcpu.txt`
what I'm telling is that the name after "$MACHINE" must match the name
used in TESTS2RRD and NCV_foobar. I think you're mixing the name of a
status (or data) report (here "pcpu") and the name of a particular line
(or data source, or DS) in the body of that status/data message.

Regards,

-- 
Charles Goyard - user-98f9625a7a59@xymon.invalid - (+33) 1 45 38 01 31
list Shifter · Wed, 8 Nov 2006 11:50:31 -0800 ·
Ahhhh, that makes sense.  Changing my client script to:

$BB $BBDISP "data $MACHINE.pcpuIdle
`cat /tmp/pcpu.txt`
"

caused the rrd's to be created and populated with data.

The change suggested by Charles Jones was helpful as it caused a link to
appear on my trends page where there was no representation of my data at
all, but not the actual graph.  The link doesn't produce any graphs either,
but I'm getting closer.  I remember reading about that elsewhere in the
forums so I'll go research that a bit.  Thank you all very much for the
assistance.
quoted from Charles Goyard

Sage

On 11/8/06, Charles Goyard <user-98f9625a7a59@xymon.invalid> wrote:
Hi,

Shifter wrote :
$BB $BBDISP "data $MACHINE.pcpu
`cat /tmp/pcpu.txt`
what I'm telling is that the name after "$MACHINE" must match the name
used in TESTS2RRD and NCV_foobar. I think you're mixing the name of a
status (or data) report (here "pcpu") and the name of a particular line
(or data source, or DS) in the body of that status/data message.

Regards,

--
Charles Goyard - user-98f9625a7a59@xymon.invalid - (+33) 1 45 38 01 31

list Shifter · Wed, 8 Nov 2006 11:58:53 -0800 ·
As a final message I was able to resolve my broken graph.  The graph
definition in my hobbitgraph.cfg file was listing an incorrect .rrd file.
Adhereing to Mr. Goyard's earlier suggestion I changed the def line to
reflect the actual rrd file name (pcpuIdle.rrd) and *poof* graph appeared in
trends.  Thank you again.

Sage
quoted from Shifter

On 11/8/06, Shifter <user-312408c55c39@xymon.invalid> wrote:
Ahhhh, that makes sense.  Changing my client script to:

$BB $BBDISP "data $MACHINE.pcpuIdle
`cat /tmp/pcpu.txt`
"

caused the rrd's to be created and populated with data.

The change suggested by Charles Jones was helpful as it caused a link to
appear on my trends page where there was no representation of my data at
all, but not the actual graph.  The link doesn't produce any graphs either,
but I'm getting closer.  I remember reading about that elsewhere in the
forums so I'll go research that a bit.  Thank you all very much for the
assistance.

Sage

On 11/8/06, Charles Goyard <user-98f9625a7a59@xymon.invalid> wrote:
Hi,

Shifter wrote :
$BB $BBDISP "data $MACHINE.pcpu
`cat /tmp/pcpu.txt`
what I'm telling is that the name after "$MACHINE" must match the name
used in TESTS2RRD and NCV_foobar. I think you're mixing the name of a
status (or data) report (here "pcpu") and the name of a particular line
(or data source, or DS) in the body of that status/data message.

Regards,

--
Charles Goyard - user-98f9625a7a59@xymon.invalid - (+33) 1 45 38 01 31

list Dan Vande More · Wed, 8 Nov 2006 14:29:13 -0600 ·
Thanks for the update. It seems a good portion of the traffic on this list
deals strictly with the NCV stuff. While the documentation is good, there
are a lot of variables and certainly a lot of restrictions (underscores,
etc) that can play a vital role in whether an NCV is working or not.
Overcoming the complexity is sure a good feeling, but it's awfully
frustrating when you can't get it working.
Unfortunately, no amount of documentation is going to be able to overcome
human errors and human emotions. Even I've spent days trying to figure out
why things didn't work only to realize I was spelling ncv as nvc.

My advice for future people doing this sort of stuff is to first copy a
working example, before attempting your own tanget. You can then control for
your variables and experiment from there. Is the wiki for hobbit official
yet? Maybe we can use that for bootstrapping our fellow hobbitiers?

-Dan
quoted from Shifter


On 11/8/06, Shifter <user-312408c55c39@xymon.invalid> wrote:
As a final message I was able to resolve my broken graph.  The graph
definition in my hobbitgraph.cfg file was listing an incorrect .rrd file.
Adhereing to Mr. Goyard's earlier suggestion I changed the def line to
reflect the actual rrd file name ( pcpuIdle.rrd) and *poof* graph appeared
in trends.  Thank you again.

Sage

On 11/8/06, Shifter <user-312408c55c39@xymon.invalid > wrote:
Ahhhh, that makes sense.  Changing my client script to:

$BB $BBDISP "data $MACHINE.pcpuIdle
`cat /tmp/pcpu.txt`
"

caused the rrd's to be created and populated with data.

The change suggested by Charles Jones was helpful as it caused a link to
appear on my trends page where there was no representation of my data at
all, but not the actual graph.  The link doesn't produce any graphs either,
but I'm getting closer.  I remember reading about that elsewhere in the
forums so I'll go research that a bit.  Thank you all very much for the
assistance.

Sage

On 11/8/06, Charles Goyard < user-98f9625a7a59@xymon.invalid> wrote:
Hi,

Shifter wrote :
$BB $BBDISP "data $MACHINE.pcpu
`cat /tmp/pcpu.txt`
what I'm telling is that the name after "$MACHINE" must match the name
used in TESTS2RRD and NCV_foobar. I think you're mixing the name of a
status (or data) report (here "pcpu") and the name of a particular
line
(or data source, or DS) in the body of that status/data message.

Regards,

--
Charles Goyard - user-98f9625a7a59@xymon.invalid - (+33) 1 45 38 01 31