Hi all: Over the years there has been numerous discussions about putting Ganglia metrics into a relational database such as MySQL. I would like to bring that discussion up again but just focus on the schema design.
There are two ideas that we can work with: 1) 1 table per host/metric The table will most likely have around 4 columns: host, metric, timestamp, value, etc.. This approach allows you to pre-define the datatype of the metric (could be int, float, etc.). But this way if you are monitoring 30 metrics from 1000 hosts, you will have 30,000 tables. You will probably also have other tables having relations between grids, clusters and hosts, etc. 2) 1 flat table for all metrics This suggestion is from Spike and the idea is you store values as string and also have another column for the datatype. If you have any other ideas, please throw them into the mix here. The schema design would also largely be affected by the desired usage of these metrics data. Cheers, Bernard ------------------------------------------------------------------------------ Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d _______________________________________________ Ganglia-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ganglia-general
