Re: [Ganglia-developers] Protocol Efficiency Ideas

2012-02-03 Thread Alex Dean
On Feb 3, 2012, at 10:18 AM, Vladimir Vuksan wrote: > It may be simple to export a simple hash table however you have to worry > about encoding. For example we have had issues with XML export in gmond > where if you sent metrics with e.g. < or > things would break since XML tags > would break. S

Re: [Ganglia-developers] Protocol Efficiency Ideas

2012-02-03 Thread Vladimir Vuksan
lookers may not be able to tell the difference."  Mark Twain __ From: Dave Rawks To: ganglia-developers@lists.sourceforge.net Sent: Friday, January 27, 2012 6:09 PM Subject: Re: [Ganglia-developers] Protocol Efficiency Ideas On 1/27/12

Re: [Ganglia-developers] Protocol Efficiency Ideas

2012-01-30 Thread Peter Phaal
developers@lists.sourceforge.net > Sent: Friday, January 27, 2012 6:09 PM > Subject: Re: [Ganglia-developers] Protocol Efficiency Ideas > > On 1/27/12 2:05 PM, Im Root wrote: > > I forgot to add that by adding json, you will be restricting the types > > of Linux that th

Re: [Ganglia-developers] Protocol Efficiency Ideas

2012-01-30 Thread Im Root
awks To: ganglia-developers@lists.sourceforge.net Sent: Friday, January 27, 2012 6:09 PM Subject: Re: [Ganglia-developers] Protocol Efficiency Ideas On 1/27/12 2:05 PM, Im Root wrote: > I forgot to add that by adding json, you will be restricting the types > of Linux that this platform runs

Re: [Ganglia-developers] Protocol Efficiency Ideas

2012-01-29 Thread Kostas Georgiou
On Sun, Jan 29, 2012 at 08:10:08AM -0500, Jeff Buchbinder wrote: > On Sat, Jan 28, 2012 at 11:21 PM, Kostas Georgiou > wrote: > > On Fri, Jan 27, 2012 at 06:59:06AM -0800, Im Root wrote: > > > >> I believe that adding json would be a mistake. The reason is that when > >> users install the main pa

Re: [Ganglia-developers] Protocol Efficiency Ideas

2012-01-29 Thread Jeff Buchbinder
On Sat, Jan 28, 2012 at 11:21 PM, Kostas Georgiou wrote: > On Fri, Jan 27, 2012 at 06:59:06AM -0800, Im Root wrote: > >> I believe that adding json would be a mistake. The reason is that when >> users install the main package there would be now a dependency on >> having json installed. It just add

Re: [Ganglia-developers] Protocol Efficiency Ideas

2012-01-28 Thread Kostas Georgiou
On Fri, Jan 27, 2012 at 06:59:06AM -0800, Im Root wrote: > I believe that adding json would be a mistake. The reason is that when > users install the main package there would be now a dependency on > having json installed. It just adds to the complexity and helps to > perpetuate RPM hell. I've had

Re: [Ganglia-developers] Protocol Efficiency Ideas

2012-01-27 Thread Peter Phaal
__ >> From: Im Root >> To: Dave Rawks ; "ganglia-developers@lists.sourceforge.net" >> >> Sent: Friday, January 27, 2012 9:59 AM >> Subject: Re: [Ganglia-developers] Protocol Efficiency Ideas >> I beli

Re: [Ganglia-developers] Protocol Efficiency Ideas

2012-01-27 Thread Dave Rawks
On 1/27/12 2:05 PM, Im Root wrote: > I forgot to add that by adding json, you will be restricting the types > of Linux that this platform runs on. Although it may be a "nice to have" > feature for a few developers who may want to customize things, this puts > an additional dependency on the platfor

Re: [Ganglia-developers] Protocol Efficiency Ideas

2012-01-27 Thread Vladimir Vuksan
ceforge.net Sent: Thursday, January 26, 2012 2:34 PM Subject: [Ganglia-developers] Protocol Efficiency Ideas Hey All,     We've been talking about adding json in addition to xml for the tcp listen port exchange format. And I was curious if the "EXTRA_DATA" subtree to the XML ever con

Re: [Ganglia-developers] Protocol Efficiency Ideas

2012-01-27 Thread Im Root
2012 9:59 AM Subject: Re: [Ganglia-developers] Protocol Efficiency Ideas I believe that adding json would be a mistake. The reason is that when users install the main package there would be now a dependency on having json installed. It just adds to the complexity and helps to perpetuate RPM hel

Re: [Ganglia-developers] Protocol Efficiency Ideas

2012-01-27 Thread Gladish, Jacob
> > On Thu, Jan 26, 2012 at 14:34, Dave Rawks wrote: > > Hey All, > >We've been talking about adding json in addition to xml for the > > tcp listen port exchange format. And I was curious if the "EXTRA_DATA" > > subtree to the XML ever contains something aside from > "EXTRA_ELEMENTS" > > a

Re: [Ganglia-developers] Protocol Efficiency Ideas

2012-01-27 Thread Jeff Buchbinder
On Fri, Jan 27, 2012 at 9:59 AM, Im Root wrote: > I believe that adding json would be a mistake. The reason is that when users > install the main package there would be now a dependency on having json > installed. It just adds to the complexity and helps to perpetuate RPM hell. > I've had to deal

Re: [Ganglia-developers] Protocol Efficiency Ideas

2012-01-27 Thread Jesse Becker
On Thu, Jan 26, 2012 at 14:34, Dave Rawks wrote: > Hey All, >        We've been talking about adding json in addition to xml for the tcp > listen port exchange format. And I was curious if the "EXTRA_DATA" > subtree to the XML ever contains something aside from "EXTRA_ELEMENTS" > and if the "EXTRA

Re: [Ganglia-developers] Protocol Efficiency Ideas

2012-01-27 Thread Dave Rawks
On 1/27/12 7:43 AM, Alex Dean wrote: > 1. As a user, I sometimes want to consume ganglia data in other > contexts (not just in gweb). I'd much prefer working with JSON > instead of XML. I think that most developers would prefer json to xml, if for no other reason than json libraries/modules are

Re: [Ganglia-developers] Protocol Efficiency Ideas

2012-01-27 Thread Dave Rawks
On 1/27/12 7:24 AM, Gladish, Jacob wrote: > > > If you want access to that metric data in JSON format, the quickest > way, by far, is to write a small conversion utility that fetches data > from the gmetad. I can imagine a perl script running in Apache/CGI > that does it on demand. You'd then have

Re: [Ganglia-developers] Protocol Efficiency Ideas

2012-01-27 Thread Dave Rawks
On 1/27/12 6:59 AM, Im Root wrote: > I believe that adding json would be a mistake. The reason is that when > users install the main package there would be now a dependency on having > json installed. It just adds to the complexity and helps to perpetuate > RPM hell. I've had to deal with installin

Re: [Ganglia-developers] Protocol Efficiency Ideas

2012-01-27 Thread Alex Dean
On Jan 27, 2012, at 8:59 AM, Im Root wrote: > I believe that adding json would be a mistake. The reason is that when users > install the main package there would be now a dependency on having json > installed. It just adds to the complexity and helps to perpetuate RPM hell. > I've had to deal

Re: [Ganglia-developers] Protocol Efficiency Ideas

2012-01-27 Thread Gladish, Jacob
26, 2012 7:38 PM > To: Bryan Thompson > Cc: ganglia-developers@lists.sourceforge.net > Subject: Re: [Ganglia-developers] Protocol Efficiency Ideas > > On 01/26/2012 02:02 PM, Bryan Thompson wrote: > > Ok. > > > > Not sure if this matters to your proposal, but GROUP is

Re: [Ganglia-developers] Protocol Efficiency Ideas

2012-01-27 Thread Im Root
been awful. It may be nice for a developer but not so nice for the end users. From: Dave Rawks To: ganglia-developers@lists.sourceforge.net Sent: Thursday, January 26, 2012 2:34 PM Subject: [Ganglia-developers] Protocol Efficiency Ideas Hey All,     We'

Re: [Ganglia-developers] Protocol Efficiency Ideas

2012-01-26 Thread Dave Rawks
On 01/26/2012 02:02 PM, Bryan Thompson wrote: > Ok. > > Not sure if this matters to your proposal, but GROUP is not always a > single name/value pair. There can be multiple GROUPs for a metadata > record. If there is more than one value for GROUP it could be an array instead of a string, That'd

Re: [Ganglia-developers] Protocol Efficiency Ideas

2012-01-26 Thread Bryan Thompson
glia-developers@lists.sourceforge.net > Subject: Re: [Ganglia-developers] Protocol Efficiency Ideas > > On 01/26/2012 01:16 PM, Jeff Buchbinder wrote: > > On Thu, Jan 26, 2012 at 4:09 PM, Bryan Thompson > wrote: > >> Dave, > >> > >> I thought that the web UI was driven t

Re: [Ganglia-developers] Protocol Efficiency Ideas

2012-01-26 Thread Dave Rawks
On 01/26/2012 01:16 PM, Jeff Buchbinder wrote: > On Thu, Jan 26, 2012 at 4:09 PM, Bryan Thompson wrote: >> Dave, >> >> I thought that the web UI was driven this way. Or is it gmond providing the >> XML output for the web UI (rather than gmetad)? > The web UI is driven that way, but gmetad is p

Re: [Ganglia-developers] Protocol Efficiency Ideas

2012-01-26 Thread Jeff Buchbinder
On Thu, Jan 26, 2012 at 4:09 PM, Bryan Thompson wrote: > Dave, > > I thought that the web UI was driven this way.  Or is it gmond providing the > XML output for the web UI (rather than gmetad)? IIRC, gmetad is currently producing XML which is consumed by the web UI. That being said, I'd prefer

Re: [Ganglia-developers] Protocol Efficiency Ideas

2012-01-26 Thread Bryan Thompson
hompson > Cc: ganglia-developers@lists.sourceforge.net > Subject: Re: [Ganglia-developers] Protocol Efficiency Ideas > > On 01/26/2012 12:07 PM, Bryan Thompson wrote: > > Dave, > > > > There is undoubtably fat in the XML. However, I think that > you would get far mo

Re: [Ganglia-developers] Protocol Efficiency Ideas

2012-01-26 Thread Dave Rawks
On 01/26/2012 12:07 PM, Bryan Thompson wrote: > Dave, > > There is undoubtably fat in the XML. However, I think that you would get far > more savings by giving the client a means to request which data they are > interested in. Right now it sends everything each time, right? It would be > nice

Re: [Ganglia-developers] Protocol Efficiency Ideas

2012-01-26 Thread Bryan Thompson
pandora.com] > Sent: Thursday, January 26, 2012 2:34 PM > To: ganglia-developers@lists.sourceforge.net > Subject: [Ganglia-developers] Protocol Efficiency Ideas > > Hey All, > We've been talking about adding json in addition to xml > for the tcp listen port exchang

[Ganglia-developers] Protocol Efficiency Ideas

2012-01-26 Thread Dave Rawks
Hey All, We've been talking about adding json in addition to xml for the tcp listen port exchange format. And I was curious if the "EXTRA_DATA" subtree to the XML ever contains something aside from "EXTRA_ELEMENTS" and if the "EXTRA_ELEMENTS" ever have attributes aside from "NAME" and "VAL"