The Ganglia Development Team is happy to announce the release of Ganglia 3.3.6. This release fixes the following bug:
BUG327: memory leak when receive channel is not configured or not hearing any data
The Ganglia Development Team is happy to announce the release of Ganglia 3.3.5. This is mainly a bugfix release for 3.3.1 and all users of the 3.3.x series are encouraged to upgrade.
Work is already under way for the next release, please stay tuned for upcoming enhancements to the project!
As part of our upcoming release of Ganglia 3.3.2 you will have the ability to add a trend line to any host metric. Let’s say you wanted to know when you will need to add more disk space to a particular machine.
We are “safe” for about a year. Or let’s say you wanted to see how your web server 90th percentile has trended.
This takes calculates trend based on last six month of data (which is a default). That looks pretty good however let’s see how it looks if we take 12 months of data
Not so good. Trending interface has easy controls that allow you to easily change how far to extend the trend line and how far back to go
We are happy to announce release of Ganglia 3.3.1. This release provides several enhancements to our web frontend as well as additional capabilities for exporting data to Graphite.
We are happy to announce the release of Ganglia 3.3.0. Highlights of this release are
- Ganglia Monitor Core is now shipped with our second generation Ganglia Web UI.
- Gmetad Daemon now supports sending metrics to Graphite (carbon)
- sFlow supports additional metric sources such as JMX, memcache, Apache
- Gmond now comes bundled with a number of additional metrics e.g. disk statistics, network interface utilization etc.
Full Release notes can be found on Github.
You can download the release from SourceForge.
Please report any issues with the release to our GitHub issue tracker.
Patrick Debois has kicked of an interesting set of projects to put metric information on a common “bus”. For example he has implemented a ruby based daemon that parses Ganglia gmond packets and puts them on a ZeroMQ pub/sub bus. Once it’s there you can “subscribe” with a client of your choice and do transforms to the data e.g.
- feed graphite or another monitoring tool
- insert data into a SQL database
- feed Nagios using passive checks
Thanks to Patrick for a great idea and implementation. Now let’s get to work on useful subscribers.
Today we released version 2.2.0 of the Ganglia Web interface. New features present in this release are described in our “Upcoming Web Features post“.
Release can be downloaded from https://sourceforge.net/projects/ganglia/files/gweb/2.2.0/
If you need help installation guide is here.
We have been working hard on new Ganglia Web features that will be part of Ganglia Web 2.2.0. These are the highlights
Allows you to compare hosts across all the matching metrics (this can mean hundreds of graphs ). You supply a regular expression that matches a set of the hosts and Ganglia will aggregate all hosts for each metric. This is useful in those cases where you are trying to find why a particular host or hosts are performing differently then another set.
Built-in Nagios integration
This feature allows you to use your Ganglia trending data to alert in Nagios. There a couple nice addition to the basic check functionality e.g.
- Check heartbeat – as you may know gmond daemons sends a periodic heartbeat (every 20 seconds by default). If the heartbeat is missing it is fair to assume host is down. This should avoid you from having to use things like check_ping and alert you to potential down time much quicker
- Check multiple metrics – allows you to use a single check to multiple metrics on the same host ie. check that disk free on / is more than 30%, on /tmp more than 10% etc.
- Check single metric across multiple hosts (not yet implemented) – use a single check to check low disk space on a set of hosts defined by a regular expression e.g. instead of having separate disk checks for every host you would have a single check that would give you a break down of hosts that were not OK.
If you want to peak at how basic check_metric alert works check out Ganglia Nagios integration wiki document.
Aggregate graphs decomposition
While viewing aggregate graphs with more than 6-7 items colors will start to blend together and it may be hard to distinguish what on graph is what. This feature allows you to decompose a graph by taking every item on the aggregate graph and putting it on a separate graph e.g. a graph like this
will decompose into this
Flot client side rendering
In this release we are turning on utilization heatmaps instead of the old style pie charts e.g.
Most of the features have already been implemented. We are still polishing up the release and writing documentation. We could always use more help with testing and documenting things so if you are up to it please join us on Freenode channel #ganglia.
If you’d like to test drive some of these changes please visit our demo site.
Today we released version 2.1.8 of the Ganglia Web interface. Following changes are present in this release
- Better way of showing all metrics when metric groups are initially collapsed. You can see the new behavior if you set $conf['metric_groups_initially_collapsed'] = true;
- Fix for broken graph zooming
- Show graph name in autorotation
Release can be downloaded from https://sourceforge.net/projects/ganglia/files/gweb/2.1.8/
We have identified a bug that prevents host overview from working. This has been fixed in Ganglia Web 2.1.7.
Release can be downloaded from https://sourceforge.net/projects/ganglia/files/gweb/2.1.7/