Version 1.1.8 of Better Cacti Templates releasedSat, Jan 22, 2011 in Monitoring Databases Operations Programming
I’ve released version 1.1.8 of the Better Cacti Templates project. This release includes a bunch of bug fixes and several important new graphs. There are graphs for the new response-time statistics exposed in Percona Server, and a new set of graphs for MongoDB.
VividCortex is the startup I founded in 2012. It’s the easiest way to monitor what your servers are doing in production and I consider it far superior to Cacti. VividCortex offers MySQL performance monitoring and PostgreSQL performance management among many other features.
There are upgrade instructions on the project wiki for this and all releases. There is also a comprehensive tutorial on how to create your own graphs and templates with this project. Use the project issue tracker (not the comments on this post!) to view and report issues, and use the project mailing list to discuss the templates and scripts.
The full changelog follows.
2011-01-22: version 1.1.8 * The cache file names could conflict due to omitting --port (issue 171). * Load-average parsing did not work correctly at high load (issue 170). * The --mpds option to make-template.pl did not create new inputs (issue 133). * The url and port were reversed in the Nginx commandline (issue 149). * Added $nc_cmd to ss_get_by_ssh.php (issue 154, issue 152). * InnoDB Transactions and other graphs showed NaN instead of 0 (issue 159). * Added graphs for Percona Server response-time distribution (issue 158). * Added graphs for MongoDB (issue 136). * Added a minimum option to the template construction logic (issue 169). * Added memtotal for Memory (issue 146). * make-template.pl sanity checks were too strict (issue 168).
I'm Baron Schwartz, the founder and CEO of VividCortex. I am the author of High Performance MySQL and lots of open-source software for performance analysis, monitoring, and system administration. I contribute to various database communities such as Oracle, PostgreSQL, Redis and MongoDB. More about me.