On Mon, Oct 06, 2008 at 11:11:51AM -0600, Brad Nicholes wrote:
> >>> On 10/3/2008 at 12:23 PM, in message
> >
> > Am I expected to deal with each SPOOF_HOST when a call_back occurs
> > for a particular metric name?
> >
> > I kind of expected SPOOF_NAME to be in the 'name' argument of the
> > call_back.
> >
>
> For the spoof modules that I wrote, I appended the host name to the
> name of the metric and used it as a unique metric identifier
>
> metric_name = name + ':' + host_name
>
> Then in the handler I just call
>
> metric_keys = name.split(':')
>
> and I end up with an array that uniquely identifies which metric for
> which host. Finally, to make sure that the concatenation of the
> metric_name:host_name does not show up in the front end as the title
> of the graph, I make sure to assign a title to the metric in the
> gmond.conf file.
>
> This is just one way to uniquely identify any spoofed metric. Since
> gmond has no idea what a metric module is doing or what naming
> convention is being used, it simply leaves all of that up to the
> module itself rather than trying to enforce some policy.
Does this not also mean I need to know at gmond start-up time which
hosts the module will be spoofing for and rewrite
/etc/ganglia/conf.d/<module>.pyconf to reflect the list of nodes that
will need to be spoofed?
mh
-------------------------------------------------------------------------
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-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ganglia-general
