I haven't checked the code to look into why it returns full XML output on non-matches however I would recommend taking a look at the Nagios integration with Ganglia Web that could provide you with similar functionality
https://github.com/ganglia/ganglia-web/tree/master/nagios Vladimir On Tue, 25 Sep 2012, Mikko Herranen wrote: > I would like to ask about the gmetad query interface. If you try to query > a non-existent subtree, you get the entire xml dump in return. This is > because the process_path function in server.c contains code that returns > the entire xml dump whenever a part of the query path is not recognized. > Is this really intentional and what is the rationale for that? Could it be > changed to return nothing? > > I'm asking because we use the query interface to reduce network traffic > when we need only a single metric. Unfortunately, we don't know in advance > which nodes have which metrics. If we query for a node/metric combination > that does not exist, we get the full xml dump which is counterproductive. > > There are ways to fix this on our side, such as keeping track of the > available node/metric combinations. However, they are not as clean as > fixing the root cause, assuming it can be fixed. ------------------------------------------------------------------------------ How fast is your code? 3 out of 4 devs don\\\'t know how their code performs in production. Find out how slow your code is with AppDynamics Lite. http://ad.doubleclick.net/clk;262219672;13503038;z? http://info.appdynamics.com/FreeJavaPerformanceDownload.html _______________________________________________ Ganglia-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ganglia-developers
