Same thing for us. Reverting the central gmetad to 3.1.7 (leaving all
nested gmetad at 3.2 - 3.3.1) goes back to the intended behavior (scalable
ON).
DL
On Sun, Feb 26, 2012 at 6:30 PM, Vladimir Vuksan wrote:
> I am suspecting support for tagging has something to do with this. I will
> need to
Hi,
We're doing this by writing a json file in the ganglia web conf dir:
clustername.json
{
"included_reports": [
"cpu_report",
"load_report",
"mem_report",
"network_report"
]
DL
On Tue, Nov 8, 2011 at 8:05 AM, Baker D.J. wrote:
> Hello,
>
> I'm new to the ganglia lists,
FWIW I see the same behavior, we're on 3.2.0 exclusively.
On Thu, Oct 13, 2011 at 3:29 PM, Mark Wagner wrote:
> Hello,
>
> After upgrading from 3.1.7 to 3.2.0 those data sources that are other
> gmetad processes no longer work properly. When I telnet to the gmetad
> source I see all the data. Th
We've got a number of large grids that we'd like to aggregate together in a
"grid of grids" display. Searching through the list and the docs, it appears
that this is possible but I can't figure out why it isn't working for us.
We're using unicast and want to do something like this:
"Global Grid"
I wanted to add to the original thread regarding bogus spikes in network
graphs, which were suspected to be caused by broadcom NICs that ship with
many of the HP Proliant series servers today. We're running HP BL460G6, with
vmware ESXi 4.1u1 hypervisors, and RHEL5.3 x64 guests. Using gmond-3.2 buil
5 matches
Mail list logo
