On Tue, Jun 1, 2010 at 11:52, Art Peck <arthurp...@aol.com> wrote: > > I am very impressed with Ganglia 3.1.7. I would like to create an addon > package to facilitate monitoring of the Oracle Sun Ray Server Software and > associated desktop devices. > > I've already created one Python module and integrated it into gmond and > gmetad. For the most part, it is working as I wanted. However, I would really > like to be able to manipulate the formatting of the resulting graph(s). For > example, I would greatly prefer a line graph to an area and I really need to > STACK several metrics on a graph. So I have the follow RFE's:
Writing custom graphing modules has been more easily supported for several releases now. If you have need to create customized charts (like many of us do), there is a well documented framework for doing so. Take a look at the various *_report.php files in the web/graph.d directory of your ganglia installation. I've specifically written a storage report script that uses stacked graphs. > (1) Extend the descriptor dictionary to include key=value pairs that get > passed to gmetd and the web frontend allowing for specification of more of > the rrdgraph formatting options. Maybe something like 'graph_type' = 'Line', > 'line_color' = 'Red', 'background_color' = 'Lt Blue', etc I believe that you could "fake" this already using string metrics. > (2) Extend gmond/gmetad and the web frontend to interpret a descriptor that > is a collection of dictionaries as meaning that the metrics described should > be stacked on one graph. Gmond has nothing directly to do with drawing the graphs, and it will almost certainly remain that way; its sole job is collect and send metrics. Gmetad has several tasks (collect/receive metrics, write RRD files, spew XML), and only one of them is tangentially related to drawing graphs (spewing XML). Almost all of the work for graph drawing is done by the various .php files, as mentioned above. The proper place to interpret such metadata (line color information, etc) as you proposed is in the reporting step. This could, in thory, be pulled out of the XML stream from gmetad. > > (3) Allow for collection of strings that are not reported by the web frontend > but rather stored by rrdtool for other reporting tasks. For example, > configuration management, in this case simple firmware version reporting, and > inventory management. RRD files cannot, so far as I am aware, cannot store this sort of data. Gmond is able to collect this sort of information, and Gmetad is able to report on it via the XML stream. I suggest that you parse out the various bits of configuration information and store them in something appropriate of your choosing. This is a good idea--don't get me wrong--and a lot of people could make use of a program that did somethign like this. Please post any modules or add-ons that you come up with. -- Jesse Becker Every cloud has a silver lining, except for the mushroom-shaped ones, which come lined with strontium-90. ------------------------------------------------------------------------------ _______________________________________________ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
