Re: [collectd] Plugins values
On Friday, February 8, 2013, Frédéric Pégé wrote: > Hi, > and thanks for the answer. > As for the tendency, I would prefer the mutliple datasource way. I still > don't get why all the values have to end in ".value", and be in separate > "folders". But nevermind. > As long as it is done the same way in every plugin, it's more logical. > This is the key. The inconsistent layout is a killer for people writing collectd+rrdtool front ends. It means you need to support two different lookup logic. -- w: http://holmwood.id.au/~lindsay/ t: @auxesis ___ collectd mailing list collectd@verplant.org http://mailman.verplant.org/listinfo/collectd
Re: [collectd] Plugins values
On Fri, Feb 08, 2013 at 11:56:08AM +0100, Frédéric Pégé wrote: > Can I help in any way possible ? > df, load, cpu, ... and other "standards" plugin are in C, right ? Yes, and the change is trivial. The decision to make incompatible changes isn't. ___ collectd mailing list collectd@verplant.org http://mailman.verplant.org/listinfo/collectd
Re: [collectd] Plugins values
Hi, and thanks for the answer. As for the tendency, I would prefer the mutliple datasource way. I still don't get why all the values have to end in ".value", and be in separate "folders". But nevermind. As long as it is done the same way in every plugin, it's more logical. Can I help in any way possible ? df, load, cpu, ... and other "standards" plugin are in C, right ? Fred. 2013/2/8 Fabien Wernli > Hi, > > On Thu, Feb 07, 2013 at 01:33:19PM +0100, Frédéric Pégé wrote: > > The load values are returned in 3 different values under the same item. > > load/load. Values are longterm, shortterm and midterm. And I'm ok with > that. > > Just my two cents on loadavg: IMHO it's totally useless to keep anything > else than shortterm, if you're using some kind of historization like > rrdtool, as you'll get the two others for free. > midterm/longterm are only useful when no history is available, > e.g. from the command line, or if you're using some kind of realtime > visualization. > > > Do you have an explanation for these different ways ? > > Anyways, back to your real question: > The reason for the differences is purely historical. The tendency is to > move > away from multiple datasources (like load, if_octets, etc.) and use only > simple datasources, like gauge, cpu, etc. > > Maybe this will happen in collectd 6, if two wisely chosen guys have the > courage to do so ;-) > > > ___ > collectd mailing list > collectd@verplant.org > http://mailman.verplant.org/listinfo/collectd > -- Linux: Rejoins-nous, nous sommes déjà 11. ___ collectd mailing list collectd@verplant.org http://mailman.verplant.org/listinfo/collectd
Re: [collectd] Plugins values
Hi, On Thu, Feb 07, 2013 at 01:33:19PM +0100, Frédéric Pégé wrote: > The load values are returned in 3 different values under the same item. > load/load. Values are longterm, shortterm and midterm. And I'm ok with that. Just my two cents on loadavg: IMHO it's totally useless to keep anything else than shortterm, if you're using some kind of historization like rrdtool, as you'll get the two others for free. midterm/longterm are only useful when no history is available, e.g. from the command line, or if you're using some kind of realtime visualization. > Do you have an explanation for these different ways ? Anyways, back to your real question: The reason for the differences is purely historical. The tendency is to move away from multiple datasources (like load, if_octets, etc.) and use only simple datasources, like gauge, cpu, etc. Maybe this will happen in collectd 6, if two wisely chosen guys have the courage to do so ;-) ___ collectd mailing list collectd@verplant.org http://mailman.verplant.org/listinfo/collectd
[collectd] Plugins values
Hi, I've just discovered Collectd, and I'm already loving it. there is nonetheless something that bugs me. The load values are returned in 3 different values under the same item. load/load. Values are longterm, shortterm and midterm. And I'm ok with that. Same with the interface bandwith. It returns rx & tx in the same item, that's fine. The Swap, memory, and many others store each value in a different item, with the value name "value". Do you have an explanation for these different ways ? Can I help ? Best regards, Fred. -- ___ collectd mailing list collectd@verplant.org http://mailman.verplant.org/listinfo/collectd
