[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
code specific rrdidx question
- To: hobbit (at) hswn.dk
- Subject: code specific rrdidx question
- From: "Jeff Newman" <jeffnewman75 (at) gmail.com>
- Date: Wed, 22 Mar 2006 12:24:08 -0600
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=ESkvE1/orrHCJLb7wm4TN0ZVluDdjDHg3IJ4WLAB+6LDE3fSxNousoXRLl3KvDyuyfRi+ruLHwX6lSIeKG5dEtsHkiOqjwrlMs71oIZndZjKWhHdEhA/UIJEtxYkpL9WMx1KikmZh9aSctkRjxtGi8nc3naDoL0vIBkSWjzA7eg=
All,
I don't know C all that well, so I need some assistance.
what are the limits/constraints of RRDIDX for graphing?
I believe the answer is buried somewhere in hobbitgraph.c
Here is my test case:
I had:
sar,cpu0.rrd
sar,cpu1.rrd
sar,cpu2.rrd
sar,cpu3.rrd
...
sar,cpu10.rrd
sar,cpu11.rrd
...
sar,cpu15.rrd
hobbitgraph.cfg:
[sar]
FNPATTERN sar,(.*).rrd
TITLE CPU sar
YAXIS %
DEF:usr (at) RRDIDX@= (at) RRDFN@:cpu (at) RRDIDX@pcntusr:AVERAGE
DEF:sys (at) RRDIDX@= (at) RRDFN@:cpu (at) RRDIDX@pcntsys:AVERAGE
DEF:wio (at) RRDIDX@= (at) RRDFN@:cpu (at) RRDIDX@pcntwio:AVERAGE
DEF:idl (at) RRDIDX@= (at) RRDFN@:cpu (at) RRDIDX@pcntidl:AVERAGE
AREA:usr (at) RRDIDX@#0000FF:@RRDPARAM (at) pcntusr
GPRINT:usr (at) RRDIDX@:LAST: \: %5.1lf (cur)
GPRINT:usr (at) RRDIDX@:MAX: \: %5.1lf (max)
GPRINT:usr (at) RRDIDX@:MIN: \: %5.1lf (min)
GPRINT:usr (at) RRDIDX@:AVERAGE: \: %5.1lf (avg)\n
STACK:sys (at) RRDIDX@#FF0000:@RRDPARAM (at) pcntsys
GPRINT:sys (at) RRDIDX@:LAST: \: %5.1lf (cur)
GPRINT:sys (at) RRDIDX@:MAX: \: %5.1lf (max)
GPRINT:sys (at) RRDIDX@:MIN: \: %5.1lf (min)
GPRINT:sys (at) RRDIDX@:AVERAGE: \: %5.1lf (avg)\n
STACK:wio (at) RRDIDX@#800080:@RRDPARAM (at) pcntwio
GPRINT:wio (at) RRDIDX@:LAST: \: %5.1lf (cur)
GPRINT:wio (at) RRDIDX@:MAX: \: %5.1lf (max)
GPRINT:wio (at) RRDIDX@:MIN: \: %5.1lf (min)
GPRINT:wio (at) RRDIDX@:AVERAGE: \: %5.1lf (avg)\n
STACK:idl (at) RRDIDX@#008000:@RRDPARAM (at) pcntidl
GPRINT:idl (at) RRDIDX@:LAST: \: %5.1lf (cur)
GPRINT:idl (at) RRDIDX@:MAX: \: %5.1lf (max)
GPRINT:idl (at) RRDIDX@:MIN: \: %5.1lf (min)
GPRINT:idl (at) RRDIDX@:AVERAGE: \: %5.1lf (avg)\n
hobbitserver.cfg has sar::1 (to only draw 1 graph per cpu) for GRAPHS,
and just regular "sar" is in TEST2RRD
sar is in the "multitest" section of hobbitcgi.cfg, as well as listed
in the extra tests section of hobbitlaunch.cfg
On a host with 4 CPU's (0,1,2,3) it draws 4 graphs
On a host with 16 CPU's (0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15)
It would draw a graph for 0,1, and broken boxes for 2,3, and no others.
SO, I removed "10,11,12,13,14,15" and outputted them to a,b,c,d,e,f
respectively.
The graphs then drew 0,1,2,3 and no more.
If I click on a specific graph, and change the "first=" to 5, it will
draw a graph for CPU4, so somewhere, the first= line isn't getting
generated correctly.
So I guess 2 questions:
1 already stated (limitations of RRDIDX - does is get confused by 1 vs
10 for example)
The other is where the first= line gets updated and why isn't it
getting updated correctly?
Any insights would be much apprieciated, as this is driving me nuts.
Thanks,
Jeff