[collectd] Patch: Support custom CPU interval v2
lee at leeh.co.uk
Tue Mar 11 08:43:04 CET 2014
It doesn't work, if I try doing this for the memory plugin (which I haven't
patched) with the following config:
This throws the following error:
Mar 11 07:28:55 rpm-i386 collectd: Found a configuration for the
`memory' plugin, but the plugin isn't loaded or didn't register a
It then logs out at 15s intervals rather than the 10s.
Is there a different approach to the fix I should be taking? I don't mind
taking another look..
On 10 March 2014 23:58, Manuel Luis Sanmartín Rozada
<manuel.luis at gmail.com>wrote:
> If I understand you problem correctly, you can use a function that
> collectd already have:
> set a plugin-specific interval for collecting metrics:
> <LoadPlugin cpu>
> Interval 60
> Or am I missing something?
> On Sun, Mar 9, 2014 at 6:47 PM, Lee Hardy <lee at leeh.co.uk> wrote:
>> I've updated the CPU interval patch to make it more generic, by adding a
>> plugin_update_interval() function called as part of the config function so
>> I can update other plugins more easily.
>> When the aggregation module is enabled for CPU information though, it
>> seems to be throwing an error:
>> Mar 9 17:22:36 rpm-i386 collectd: plugin_value_list_clone: Unable
>> to determine interval from context for value list
>> "rpm-i386.build.local/aggregation-cpu-average/cpu-idle". This indicates a
>> broken plugin. Please report this problem to the collectd mailing list or
>> at <http://collectd.org/bugs/>.
>> This seems to happen even when I specify the interval via
>> plugin_register_complex_read() as well, so I'm not entirely sure if I've
>> missed something or there is some issue with the aggregation module.
>> Anyone have any ideas?
>> Lee H
>> collectd mailing list
>> collectd at verplant.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the collectd