README$Revision: 1.6 $, $Date: 2000/04/04 16:35:25 $.
RRGrapher is a front-end for RRDTOOL that allows you to interactively build
graphs of your own design. Also it allows you the freedom to use any
combination of other RRDTOOL frond-ends such as MRTG, Cricket, and 14all to
create and maintain the
.rrd files, but generate graphs containing data from any of those sources in the
I originally wrote this tool in 1999, and upon releasing FlowScan-1.002,
another front-end of mine for RRDTOOL, I realized that I use RRGrapher all
the time and it'd be nice if FlowScan users had access to it so they didn't
go criminally insane trying to maintain
rrdtool graph command lines by following the examples in FlowScan's
You should receive an automatic response that will request that you verify your request to become a member of the list, to which you must reply with the authentication information there-in. Then, in response to your reply, you should receive a welcome message. If you have any questions about the administrative policies of this list's manager, please contact:
* perl version 5 * RRDTOOL
CONFIGURATION SECTION(near the top) and then install it as ``.cgi'' script for the web server (e.g. Apache) running
*onthe same machine* as where the
If you don't have, or want, Apache on the same machine as where you produce
.rrd files, I've found it convenient to simply scp or rcp the
.rrd files over to the web server periodically via cron.
1) You should see a list of Available Databases - these are the ".rrd" files that you configured. Select one or more of these which contain the data sources that you'd like to graph. 2) If the Database contains multiple Data Sources of different types, such as bytes and packets which wouldn't make sense to attempt to plot on the same graph, consider using the "Data Source RegExp" to limit which Data Sources will be selected when you click "Add>>". E.g. I often enter "bytes" as the regular expression when using ".rrd" files created by FlowScan. One might enter "ds" as the filter to get just in and out octets with Cricket-produced Databases.
3) Click "Add>>" to select the Data Sources.
4) Choose the "Plot Type". I often use "AREA" for the first Data Source, and "STACK" for all the subsequent Data Sources.
5) If desired, change the color selections. Clicking "Update Colors" isn't necessary unless you want to see them before generating the graph.
6) Add a Data Source of your own, using an RPN expression. This is an advanced option, you must understand RRDTOOL's graph feature to do this. An example would be to enter "A,B,+,0.000007629394,*" to add source A and B, then convert from bytes to megabits.
7) Click either "Graph Data Sources" or "Graph Data Sources to GIF" to produce the graph. I find myself almost always using the former since it results in the graph being displayed above the rest of the user-interface. "Graph Data Sources to GIF" is more suitable if you want to save the results to a file using your web browser.
8) You can continue to use the above steps to tweak the graphs as you'd like.
9) Once you have something you like, add it to your "Bookmarks" or "Favorites" of your web browser.
10) To do an entirely different graph, I'd suggest starting all over.
RRGrapher is slow on some machines, on some network connections, and with some web browsers.
Its performance is partly based on the number of
rrd files you make available to it in your configuration. Currently, it's
faster to tell it to look in the ``leaf'' node directories than to have it
recursively find all files under a ``root'' directory hierarchy, such as
``cricket-data''. I expect to speed this up in future revisions.
Slowness is also due in part to RRGrapher being a simple CGI - no fancy databases helping it along or anything. It sometimes causes hundreds of Kbytes to be exchanged between the web server and browser. I'm making the browser do all the work by storing all the graph options in the form and in hidden fields.
In the mean time, one way to speed things up once you've got a graph you like is to bookmark the URL of just the GIF output itself (i.e. use the ``Graph Data Source to GIF'' rather than simple the ``Graph Data Source'' button).
Copyright (c) 2000 Dave Plonka <firstname.lastname@example.org>. All rights reserved.
This document may be reproduced and distributed in its entirety (including this authorship, copyright, and permission notice), provided that no charge is made for the document itself.