headers
Keith Sinclair | 6 Jun 2002 03:39
Picon

Re: PIE CHART ???


Michael,

I have done some graphs with GD::Graph which is pretty nice.  I have also
written some code to dump an RRD to a perl hash (ass. array) so combining
these two bits you could have a Pie Chart pretty quickly.  Code below, needs
tie'ing together but should be enough, would need to massage the data a
little before sticking into a PIE chart, need to do some quick
consolidation/summarisation, I have been meaning to whip something up but
busy with work.

Regards

Keith

# get stats
my ($statval,$head) = &getRRDasHash(rrd => $rrdfile, type => "AVERAGE",
start => $args{start}, end => $args{end});

# walk stats and do something with them (prints out as CSV file)
	print "Content-type: text/plain\n\n";
	foreach my $m (sort keys %{$statval}) {
		if ($f) {
			$f = 0;
			foreach my $h ( <at> $head) {
				push( <at> line,$h);
				print STDERR " <at> line\n";
			}
			#print STDERR " <at> line\n";
			$row = join("\t", <at> line);
(Continue reading)

Permalink | Reply |
headers
Michael T. Babcock | 6 Jun 2002 14:51

Re: PIE CHART ???


That's exactly the type of thing I'm talking about.  Looks good.

Rant: I'm not sure what the emacs-like fascination is with integrating all
these things into the 'rrdtool' program itself.  A good access library to
rrd files, a good collection program, and graphing tools are of course
desired but don't all need to be in one program ...

> I have done some graphs with GD::Graph which is pretty nice.  I have also
> written some code to dump an RRD to a perl hash (ass. array) so combining
> these two bits you could have a Pie Chart pretty quickly.  Code below,
needs
> tie'ing together but should be enough, would need to massage the data a
> little before sticking into a PIE chart, need to do some quick
> consolidation/summarisation, I have been meaning to whip something up but
> busy with work.
--
Michael T. Babcock
CTO, FibreSpeed Ltd.
http://www.fibrespeed.net/~mbabcock/

--
Unsubscribe mailto:rrd-developers-request <at> list.ee.ethz.ch?subject=unsubscribe
Help        mailto:rrd-developers-request <at> list.ee.ethz.ch?subject=help
Archive     http://www.ee.ethz.ch/~slist/rrd-developers
WebAdmin    http://www.ee.ethz.ch/~slist/lsg2.cgi
Permalink | Reply |
headers
Alex van den Bogaerdt | 6 Jun 2002 15:26

Re: PIE CHART ???


Michael T. Babcock wrote:

> Rant: I'm not sure what the emacs-like fascination is with integrating all
> these things into the 'rrdtool' program itself.  A good access library to
> rrd files, a good collection program, and graphing tools are of course
> desired but don't all need to be in one program ...

There was a discussion many moons ago about separating the grapher
from the rest.  Perhaps you can dig in the archives.

cheers,
--

-- 
   __________________________________________________________________
 / alex <at> slot.hollandcasino.nl                  alex <at> ergens.op.het.net \
| work                                                         private |
| My employer is capable of speaking therefore I speak only for myself |
+----------------------------------------------------------------------+
| Technical questions sent directly to me will be nuked. Use the list. | 
+----------------------------------------------------------------------+
| http://faq.mrtg.org/                                                 |
| http://rrdtool.eu.org  --> tutorial                                  |
+----------------------------------------------------------------------+

--
Unsubscribe mailto:rrd-developers-request <at> list.ee.ethz.ch?subject=unsubscribe
Help        mailto:rrd-developers-request <at> list.ee.ethz.ch?subject=help
Archive     http://www.ee.ethz.ch/~slist/rrd-developers
WebAdmin    http://www.ee.ethz.ch/~slist/lsg2.cgi
(Continue reading)

Permalink | Reply |
headers
Michael T. Babcock | 6 Jun 2002 15:53

Re: PIE CHART ??? (long)


> There was a discussion many moons ago about separating the grapher
> from the rest.  Perhaps you can dig in the archives.

For the sake of others who don't like searching (like myself), I'll pull a
Kernel Traffic type summary here.

I see that you (Alex) posted about this subject back in August:

Alex: http://www.ee.ethz.ch/~slist/rrd-developers/msg00543.html

I see that unfortunately it was in response to Tobias himself who seems to
have the limited view of rrdtool as being a graphing utility (as opposed to
a round robin database storage system, as per its name, with many other
potential generic applications):

Tobias: http://www.ee.ethz.ch/~slist/rrd-developers/msg00541.html

Petri Helenius responded to Tobias as well, pointing out that it would be
nice for the existing graphing module in rrdtool to be able to use external
data sources (as recently requested on the list w.r.t. some MySQL-stored
data):

Petri: http://www.ee.ethz.ch/~slist/rrd-developers/msg00542.html

Tobias responded to the first post above by Alex, saying that linking the
graphing tool seperately shouldn't be a problem because of how modular the
code is, but that he didn't see the benefit of doing so as the graphing
portion is the heavyweight:
(Continue reading)

Permalink | Reply |
headers
Michael T. Babcock | 6 Jun 2002 15:53

Re: PIE CHART ??? (long)


> There was a discussion many moons ago about separating the grapher
> from the rest.  Perhaps you can dig in the archives.

For the sake of others who don't like searching (like myself), I'll pull a
Kernel Traffic type summary here.

I see that you (Alex) posted about this subject back in August:

Alex: http://www.ee.ethz.ch/~slist/rrd-developers/msg00543.html

I see that unfortunately it was in response to Tobias himself who seems to
have the limited view of rrdtool as being a graphing utility (as opposed to
a round robin database storage system, as per its name, with many other
potential generic applications):

Tobias: http://www.ee.ethz.ch/~slist/rrd-developers/msg00541.html

Petri Helenius responded to Tobias as well, pointing out that it would be
nice for the existing graphing module in rrdtool to be able to use external
data sources (as recently requested on the list w.r.t. some MySQL-stored
data):

Petri: http://www.ee.ethz.ch/~slist/rrd-developers/msg00542.html

Tobias responded to the first post above by Alex, saying that linking the
graphing tool seperately shouldn't be a problem because of how modular the
code is, but that he didn't see the benefit of doing so as the graphing
portion is the heavyweight:
(Continue reading)

Permalink | Reply |
headers
Tobias Oetiker | 6 Jun 2002 16:40
Picon
Picon
Favicon

Re: PIE CHART ??? (long)


Today Michael T. Babcock wrote:

> I see that as being _the_ reason to link it seperately, however, or to at
> least link the data collection tool seperately (the opposite approach to the
> same issue) so that it can be used quickly and easily without the graphing
> portion of the tool.
>
> If I may summarize how I see rrdtool as being potentially seperated:
> 1) A base rrd file library (including inserting, modifying and retrieving
> data)
> 2) A data collection / rrd file maintenance tool linked against (1)
> 3) Perl / other modules that use the above library (1) as well.
> 4) A graphing tool that creates graphs (in whatever way) using (1) to access
> the data, but possibly also using other data sources.
> 5) An rrdtool binary that acts as the current one does, calling the above
> programs as necessary to do its work.
> 6) Other data acquisition modules written against (1) or (2) such as
> converting from MRTG files, accessing SNMP data, etc.
>
> As I understand it, this would not be very difficult right now, and I'm not
> saying anything more than "this is how I think it would be a better overall
> tool."  The issue I believe is the seperation of 'back-end' data handling,
> 'middle-ware' to make front-ends possible and 'front-ends'.

Dear Michael,

Appart from you saying
"this is how I think it would be a better overall tool."
I can not see any point in this discussion. (And in the rrdtool
(Continue reading)

Permalink | Reply |

Gmane