Re: [Ganglia-developers] Getting code into Ganglia

2007-03-12 Thread Richard Mohr
Paul, > > I can think of a third: Logically organizing related metrics. [snip] > (As an aside, I'd point out that your use-case above is assigning additional > semantics to the "/" character: that of a separator when "flattening" a > hierarchy of metrics from a host. That's perfectly legitimat

Re: [Ganglia-developers] Getting code into Ganglia

2007-03-08 Thread Paul Millar
Hi Rick, On Tuesday 06 March 2007 15:40, Richard Mohr wrote: > On Mon, 2007-03-05 at 16:14 +, Paul Millar wrote: > > I think that, like it or loath it, people may have legitimate reasons to > > use the "/" character. The are two specific use-cases I'm thinking of: > > plotting disk-partition-

Re: [Ganglia-developers] Getting code into Ganglia

2007-03-06 Thread Richard Mohr
On Mon, 2007-03-05 at 16:14 +, Paul Millar wrote: > I think that, like it or loath it, people may have legitimate reasons to use > the "/" character. The are two specific use-cases I'm thinking of: plotting > disk-partition- and VO- statistics (but other probably exist). I can think of a t

Re: [Ganglia-developers] Getting code into Ganglia

2007-03-05 Thread Paul Millar
Hi Martin, On Monday 05 March 2007 12:54, Martin Knoblauch wrote: > I have just added the bug to my list. Unfortunatelly people are a bit > lazy in picking from the global bug-list. OK. > As for #120 I am inclined to shout "no, never " :-) What is the > need for having "/" as part of the m

Re: [Ganglia-developers] Getting code into Ganglia

2007-03-05 Thread Martin Knoblauch
Dear Paul, I have just added the bug to my list. Unfortunatelly people are a bit lazy in picking from the global bug-list. As for #120 I am inclined to shout "no, never " :-) What is the need for having "/" as part of the metrics name? This is so utterly ugly... Cheers Martin --- Paul Mill

[Ganglia-developers] Getting code into Ganglia

2007-03-02 Thread Paul Millar
Hi all, Last December, I asked about getting a bug-fix into Ganglia (bug #120, see [1]). Through the following discussion, I had thought the consensus was that the code was basically OK and was ready to go in. There was a few concerns, that the patch: might cause confusion on certain p