Thanks for the pictures, they helped me visualize the problem.
I agree with you, even in non-scalable mode, gmetad should output a GRID tag.
I have made the change to server.c, and initial tests here look good.
I have committed the gmetad changes to CVS. No changes were made to the
webfrontend
Could you take a screen snapshot and send it to me?
Just so I understand, you have a setup something like this:
gmeta (not scalable) --> gmeta (not scalable) > cluster1
On Wednesday, September 3, 2003, at 11:53 AM, Jason A. Smith wrote:
The bug I noticed is only in the web-frontend m
Were you able to reproduce this with scalable set to off?
Also, I noticed in the current version of the webfrontend, the list of
metrics that can be viewed and sorted on in the cluster view, no longer
include gmond_started & (last)reported. Why were these removed? I
briefly looked in header.php
The bug I noticed is only in the web-frontend meta view. If the
scalable is set to off then the grid summary table and plots do not show
up on the top of the page anymore. It just shows up in the middle of
the list of clusters with a blank name. On the top, and next to the
cluster selection box,
There is an inconsistency for scalability mode in the example
gmetad.conf config file and the gmetad/conf.c source file which reads
that config file. In the example config file, the option is called
"scalability" but the source is looking for an option named "scalable".
Also, if the scalable opti