ViewVC Help
View File | Revision Log | Show Annotations | Revision Graph | Root Listing
root/i-scream/experimental/reports/graphing/graph.pl
Revision 1.8 - (view) (annotate) - [select for diffs]
Sun Aug 1 10:39:49 2004 UTC (19 years, 9 months ago) by tdb
Branch: MAIN
CVS Tags: HEAD
Changes since 1.7: +2 -2 lines
Diff to previous 1.7
Catch a lot of old URL's and update them. Also remove a couple of old files
that aren't used.

Revision 1.7 - (view) (annotate) - [select for diffs]
Wed Mar 13 20:50:48 2002 UTC (22 years, 1 month ago) by tdb
Branch: MAIN
Changes since 1.6: +4 -1 lines
Diff to previous 1.6
Added a graph of "the last year". Also fixed a minor bug with the script to
create the rrd's. As an aside, I've noticed the grid on the graphs seems to
differ between the different graphs. I'm sure this is because I've got some
of my numbers a bit silly ;) oh well :)

Revision 1.6 - (view) (annotate) - [select for diffs]
Mon Mar 11 17:06:45 2002 UTC (22 years, 1 month ago) by tdb
Branch: MAIN
Changes since 1.5: +21 -9 lines
Diff to previous 1.5
Fixed the memory/swap issue. Now displays "in use" rather than free. Also
tweaked the algorithm used to make the consolidated graphs - it now does
averaging rather than just taking the maximum value over the period. This
was done because some of the graphs gave unbelievable results - cpu graphs
with a total of well over 100% looks silly ;)
Finally, ruled out being able to set the maximum for disk/mem/swap graphs
from a dynamic value. The only possibly solution would be for watch.pl to
dump out the current maximums to a file, which this could then read and
make use of (external to the RRD stuff - which would have been best). This
would, in my opinion, be silly as it would generate an awful lot more I/O
operations than is actually required.

Revision 1.5 - (view) (annotate) - [select for diffs]
Mon Mar 11 00:25:35 2002 UTC (22 years, 1 month ago) by tdb
Branch: MAIN
Changes since 1.4: +23 -11 lines
Diff to previous 1.4
Fixed the limits of the graphs a bit better (I hope). Also made some tweaks
to the colours and layout of the graphs. They're now "blue" which fits with
the i-scream look-n-feel... but do they look ok?

Revision 1.4 - (view) (annotate) - [select for diffs]
Sun Mar 10 16:40:12 2002 UTC (22 years, 1 month ago) by tdb
Branch: MAIN
Changes since 1.3: +4 -2 lines
Diff to previous 1.3
Some initial, but working, pages to fit into the i-scream reports center.
Still need work, like the drop down "type" box doesn't display disks or
queues that nicely. Maybe brings back the argument for meta-deta about each
graph in a file (like the queue's .def files maybe).

Revision 1.3 - (view) (annotate) - [select for diffs]
Sun Mar 10 03:19:57 2002 UTC (22 years, 1 month ago) by tdb
Branch: MAIN
Changes since 1.2: +27 -27 lines
Diff to previous 1.2
Another bugfix, which is actually a bit irritating. Oh well :) At least
queue's with more than one internal queue should now work.

Revision 1.2 - (view) (annotate) - [select for diffs]
Sun Mar 10 03:07:08 2002 UTC (22 years, 1 month ago) by tdb
Branch: MAIN
Changes since 1.1: +7 -6 lines
Diff to previous 1.1
Minor bug fixes.

Revision 1.1 - (view) (annotate) - [select for diffs]
Sat Mar 9 19:53:24 2002 UTC (22 years, 1 month ago) by tdb
Branch: MAIN
Graphing of most of the i-scream data. This is intended as an alternative
to the current MySQL/DBReporter style of daily graph generation.
This is split into two sections:
watch.pl connects to the i-scream client interface, parses all the data
and stores it in rrdtool database files. This is still very incomplete and
somewhat messy code :)
graph.pl generates graphs from the rrdtool database files created by the
previous script. It drops these images into a directory structure for
viewing over the web.
The php pages provide an easy way to view these graphs during development,
but it is expected in the long term to integrate this into the i-scream
reports pages.
Finally XMLParser.pm is a wrapper to the XML parsing to create i-scream
style XMLPacket hashes :)

Convenience Links

Links to HEAD: (view) (annotate)

Compare Revisions

This form allows you to request diffs between any two revisions of this file. For each of the two "sides" of the diff, select a symbolic revision name using the selection box, or choose 'Use Text Field' and enter a numeric revision.

  Diffs between and
  Type of Diff should be a