>>> On 8/29/2008 at  6:52 PM, in message <[EMAIL PROTECTED]>,
Kostas Georgiou <[EMAIL PROTECTED]> wrote:
> On Tue, Aug 26, 2008 at 09:01:43AM -0600, Brad Nicholes wrote:
> 
>>   Thanks Rich.  This got me thinking a little about how the same thing
>>   might be done only in a more generic way rather than just
>>   sequentially numbered metrics.  I am wondering if, rather than
>>   looping through numbers, we actually tried to do some pattern
>>   matching over the known metrics.  For every known metric that
>>   matches a metric pattern found in a collection_group, the metric
>>   name is constructed and the metric is added using the
>>   add_metric_series() function.  Of course it would also have to do
>>   some kind of substitution for the metric title as well.  This could
>>   simplify some of the metric configurations.
> 
> +1
> 
> Another option will be to have each module able to print some usable
> configuration. I am attaching some patch from a quick hack that I wrote
> for the multidisk plugin to output a usable .conf file. Maybe extending
> the mudule api with a metric_autoconf function so you can do a gmond -t
> modulename > modulename.conf (or something similar) is a good idea.
> It can get you going for simple setups where you just need to collect
> all available metrics.
> 

I like where you are going with the autoconf idea, but I think that we would 
probably have to move a lot of the configuration specific text into gmond 
itself.  The problem is that if for some reason a new directive were added or 
changed, it would be difficult to have to change the configuration text in 
every module's autoconf.  We could probably just add some extra autoconf data 
to the metric definition which gmond could use to produce a real configuration 
file.  This is actually one of the reasons why the metadata functionality was 
built in the way it was.  It would be very easy to just add a new metadata tag 
using the addmetadata() C function (for python modules it would just be an 
extra dictionary entry).  Gmond would then detect the extra flag and generate 
configuration file text from it.

Brad


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Ganglia-developers mailing list
Ganglia-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ganglia-developers

Reply via email to