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 installing json in the past and it's been awful.
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 access to apache's caching capability. And if
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
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 installing
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
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
On Thu, Jan 26, 2012 at 14:34, Dave Rawks d...@pandora.com 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
On Fri, Jan 27, 2012 at 9:59 AM, Im Root imr...@rocketmail.com 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.
On Thu, Jan 26, 2012 at 14:34, Dave Rawks d...@pandora.com 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
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 platform. You will be restricted to using only
I don't get it. JSON is a notation that has nothing to do with Linux.
I think addition of JSON will be fantastic and look forward to including
it.
Vladimir
On Fri, 27 Jan 2012, Im Root wrote:
I forgot to add that by adding json, you will be restricting the types of Linux
that this
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 platform.
I think a JSON option would make the gmond data more accessible. If the hood is
going to be open on the transport, an HTTP option would further open up access
to the data. HTTP would provide a way to pass query arguments and return
specific metrics, or metrics for a particular host, tag etc. I
13 matches
Mail list logo
