Quick aside first - I promised yummy patches to provide from/to time periods for graphs and other stuff (http://www.aouk83.dsl.pipex.com/), but erhh I was away from work. not done.
On our clusters the ganglia users would particularly like per processor cpu graphs as well as the combined one, for the obvious reason that you can see the difference between 1 loaded cpu and 1 idle, or all the cpus running but not so loaded. Also we use gangia to monitor more than just HPC clusters. I am not sure which way I should proceed, and the code setup for metrics is kind of discouraging against putting in new ones with XDR encoding because of the places I need to change stuff - linux/metric.c and gmond.c and ./lib/protocol_xdr.c and protocol.h at the least. Also the data structures are not condusive to a to having a variable number of processor's and thence the metrics themselves. Plan B would be to snip out the gmetric code and create gmetric style udp packets for the extra metrics, but it was not clear to me that that would be OK given that the callback stuff and the xdr codes are a bit intertwined. Any suggestions anyone? Or even let me know which may be the safest way to go. kind regards, Richard ------------------------------------------------------------------------ For more information about Barclays Capital, please visit our web site at http://www.barcap.com. Internet communications are not secure and therefore the Barclays Group does not accept legal responsibility for the contents of this message. Although the Barclays Group operates anti-virus programmes, it does not accept responsibility for any damage whatsoever that is caused by viruses being passed. Any views or opinions presented are solely those of the author and do not necessarily represent those of the Barclays Group. Replies to this email may be monitored by the Barclays Group for operational or business reasons. ------------------------------------------------------------------------
