On Wed, Mar 17, 2010 at 10:36 AM, Bob Cotton <[email protected]> wrote:
> For systems that are "far away" from collectd without access to the types
> database, it would be nice to have this info.
Agreed, looking for the same thing too.
> May I suggest a format for the JSON to incorporate this data.
> Again, using load as an example:
> [
> {"values":{"shortterm:GUAGE":0.0561523, "midterm:GUAGE":0.188477,
> "longterm:GUAGE":0.276855},
> "time":1268776516,
> "interval":10,
> "host":"host.domain.com",
> "plugin":"load",
> "plugin_instance":"",
> "type":"load",
> "type_instance":""}
> ]
> Basically changing "values" from an array to a hash, keyed by a
> "name:type".
Why change the structure of "values"? Since the count of values, DS
names, and DS types will always be the same, why not just introduce
two new arrays, "dsnames" and "dstypes"? Then the change would be
backwards compatible, and a configuration switch could be added to
enable this additional "DS metadata".
Best,
- Chris
_______________________________________________
collectd mailing list
[email protected]
http://mailman.verplant.org/listinfo/collectd
