Works for me; generating a GUID into an "alias" value in the configuration file may be the easiest way to avoid resolving things. Whether the map to something easy to debug from is from an IP address or a GUID isn't particularly material to me; I just want that map to be easy (and in my normal workflow) to maintain, and I don't want the lowest aggregation (gmond) layer to need access to that map.
-- ReC On Oct 9, 2009, at 2:15 PM, Jesse Becker wrote: > On Fri, Oct 9, 2009 at 17:05, Spike Spiegel <fsm...@gmail.com> wrote: >> As to Rick's comments I believe they are only valid if we assume that >> the string representing a host should be its ip or the fqdn resolving >> to it, which I think is one of the many problems this alias patch is >> meant to solve (instances on EC2 or with multiple interfaces are a >> pita if things rely on ips/PTR for identification). > > I'm a *huge* fan of giving admins powerful tools that do specifically > what they ask for. The admins should be clueful enough to know when > something is appropriate and when it isn't. If that means they break > their own system due to a misconfiguration, so be it. The default > setting, of course, should be to try to do the right thing--which > Ganglia does most of the time. > > Several people have asked for this feature in the last year or two, > and I (dimly) recall them all having decent, if not very good, reasons > for wanting aliasing. > >> what do we need next? people compiling gmond with this patch and >> testing? > > Yes. (myself included) > >> [1] I've seen that discussion coming up in several instances on the >> rrd ML and never go anywhere because of some big change that >> apparently would be necessary to implement that feature correctly. > > Hmm. Pity. :-( > > -- > Jesse Becker > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart > your > developing skills, take BlackBerry mobile applications to market and > stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > Ganglia-developers mailing list > Ganglia-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/ganglia-developers ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
