Hi all: I just tested hsflowd 1.11 on Windows with the latest code in trunk and run into some issues with the frontend where certain graphs like load_, cpu_ and mem_ reports are not showing up.
The reason is probably due to the fact that a recent change in the sflow integration code where unsupported metrics are not submitted. For instance, the load_* metrics are expensive to calculate on Windows and therefore are not supported. I was wondering would it be better to report these metrics with the value of 0 rather than dropping them, as they are core sets of metrics used in the frontend reports -- thoughts? Also, I think Nick was suggesting that perhaps we can try to use the Processor Queue Length on Windows for the load metric. Thanks, Bernard ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
