[Ganglia-developers] AIX Ganglia patches
Hi, has anyone applied the patches from Michael Perzl (bugzilla #224 - #227). I' m not able to test the ibmpower module as I' ve no working autoconf to create a new module. The enable shared patch from #227 can' t find libtool in my download. Can somebody help me to test the patches? Ulf -- Sensationsangebot verlängert: GMX FreeDSL - Telefonanschluss + DSL für nur 16,37 Euro/mtl.!* http://dsl.gmx.de/?ac=OM.AD.PD003K1308T4569a -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
Re: [Ganglia-developers] Possible REST interface to the interactiveport?
On Wed, Jan 21, 2009 at 2:52 AM, Brad Nicholes bnicho...@novell.com wrote: Yep, I was also thinking that a RESTful output module for gmetad-python would probably be the easiest solution I haven't used gmetad-python yet so one concern would be performances and how it'd behave having to aggregate and serve a lot of data/requests. And another question is how different/harder/easier would it be to scale a RESTful service in gmetad versus say a standalone django/pylons app. Plus it would be nice if you could request a time range or range of values instead of just current, which would require some kind of storage and leads me to what I was playing with: use memcache to store the last n values using hash(hostname+metric) as key and take advantage of expiration to clean up old stuff. At this point you can easily put together a fairly standard web service that can return last or even last-n values without adding complexity to ganglia. You could make it even smarter and make it rrd aware so that if you want older data it can be fetched from there, and you could add support for a freshness check so it pings gmetad to request last reading's timestamp and use that to validate data read from memcache, but anyway let's keep it simple for now. -- Behind every great man there's a great backpack - B. -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
[Ganglia-developers] gmetad protocol and propagating errors back to the client
Hi, right now when gmetad fails an error is logged and in some cases the connection to the client interrupted returning invalid XML or in other cases (item not found or broken request) the entire tree is returned. This imho is bad behavior and code should be added to inform the client of the error, but before that's possible it needs to be agreed how this communication should happen. I'm not really fond of XML or ganglia's code, but I'd guess adding an ERROR element to the DTD is possibly a solution. At that point whenever there's an error root_report_start() should be called at the very least and an error element added inside. This should also work nicely for the multi-item per request patch I proposed elsewhere [1] as you'd have an error per requested element. If anybody is willing to lend a hand to kickstart the XML definition (or whatever approach is best) I'd be glad to work on the rest. thanks -- Behind every great man there's a great backpack - B. -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
