>>> On 11/6/2007 at 6:06 AM, in message <[EMAIL PROTECTED]>, john allspaw <[EMAIL PROTECTED]> wrote: > Hey all - > > While I love the idea of the python module, I'd like the plain-old gmetric > binary to stay as-is. I'm not sure if there are/were plans on getting rid of > it in favor of the new custom framework stuff. Some of the reasons why I > think it should stay: > > - Gmetric makes building custom metrics insanely easy. I tell people all the > time: "if you can make a number with any script you have, you can get it into > ganglia, with whatever language you want." > > - We have a lot of custom metrics that depend on other software, (we take > results from nagios checks and spit them into ganglia with the gmetric > command, for example) and that can't be rewritten without a lot of work. > > A huge part about why some folks where I work (Yahoo!) are interested in > ganglia is that even with as basic install, you get a LOT > of visibility into your systems and network, with very little effort. Being > able to embed a one-line gmetric command into any other monitoring they > already have is the icing on the cake. > > Thoughts ?
I see no reason at all why gmetric should go away in 3.1. It is obvious that gmetric is still useful and it provides a different way to acquire metrics. Even though I prefer the python or 'C' metric interface, removing gmetric doesn't really serve any purpose. It should stay if for no other reason than for backward compatibility. Brad ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
