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
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.
Is gmetad really pulling the XML from gmond? Why not just embed the logic to
listen for UDP packets and develop a soft state model of the clus
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
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
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)?
Thanks,
Bryan
> -Original Message-
> From: Dave Rawks [mailto:d...@pandora.com]
> Sent: Thursday, January 26, 2012 4:06 PM
> To: Bryan Thompson
> Cc: gang
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
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 if you could provide a regex for what you needed. One op
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"
