On Mon, Jul 21, 2003 at 01:36:29PM -0700, Federico Sacerdoti wrote:
>
> On Monday, July 21, 2003, at 11:15 AM, Brooks Davis wrote:
>
> >>I've got to get the 2.5.4 gmetad and webfrontend out. It includes an
> >>explicit option (a button on the webpage) to turn off all graphs in
> >>the
> >>cluste
On Monday, July 21, 2003, at 11:15 AM, Brooks Davis wrote:
I've got to get the 2.5.4 gmetad and webfrontend out. It includes an
explicit option (a button on the webpage) to turn off all graphs in
the
cluster status view.
It would be really helpful if you could do it in the config file as a
d
On Mon, Jul 21, 2003 at 10:43:49AM -0700, Federico Sacerdoti wrote:
>
> On Friday, July 18, 2003, at 04:07 PM, Brooks Davis wrote:
>
> >It would be nice if setting $max_graphs in the web frontend resulted
> >in showing no graphs instead of all of them. If you change the two
> >"$max_graphs > 0"
I have written a small program that listens on the G2 multicast channel
and prints an XML snippet for every metric it hears. I have found that
it makes a great G2 Ganglia debugger and perhaps can be useful in other
situations.
Let me know if anyone is interested in this.
Federico
Rocks Clus
On Friday, July 18, 2003, at 04:07 PM, Brooks Davis wrote:
It would be nice if setting $max_graphs in the web frontend resulted
in showing no graphs instead of all of them. If you change the two
"$max_graphs > 0" lines to >= you can use -1 for all and have 0 be
useful.
I'm much happier lookin
Because of a still unexplained bug in the kernel we are running, the
numbers reported in /proc/stat suddenly jumped up the other day on us.
This exposed a bug in gmond that caused it to report bogus cpu_*
numbers. The problem is caused because the total_jiffies_func adds up
the 4 cpu states (32-b
