I just uploaded the 1.0.0 release of my MySQL templates for Cacti. Now there’s an actual download under the Downloads tab. I solved a number of issues in this release. The changelog:
2008-06-01: version 1.0.0 * Fixed when SHOW MASTER LOGS has no File_size column. * Fixed Cacti-version-specific problems with include files. * Fixed when binary log is not enabled. * Fixed some caching issues. * Fixed make-template.pl issues when downloaded from SVN. * Replication graph shows only slave_lag instead of Seconds_behind_master * Generate a version for Cacti 0.8.6i. * Support generating custom versions with make-template.pl.Technorati Tags:Cacti, monitoring, mysql
Baron,
I posted this over at the cacti forums: http://forums.cacti.net/viewtopic.php?p=138104 - but thought I’d hit you here, too:
What does it take to update these templates to be compatible with 0.8.7b (in my case)? I’m definitely not one with the internals of cacti and templating. The most I’ve done is deconstruct the db schema in order to bulk add several thousand existing RRDs from another system…
I’ve been running the xaprb templates for a month or so on a test 0.8.6x environment, and I’d love to pull it forward now that the spine kinks have been worked out. Apart from the spine issues and an ongoing ’show engine innodb status’ deadlock oveflow we’re going to try clearing tomorrow morning, the new graphs have been *great* on 8 of our production DBs. Unfortunately, the deadlock cruft is on our master production farm scheduling node, and we’re really gun-shy about screwing with that one. The last time I tried being clever with it, I took $Company down for about two and a half hours. I suck at life.
The best way I’ve found to clear out that deadlock, without impacting your server:
http://www.xaprb.com/blog/2006/08/08/how-to-deliberately-cause-a-deadlock-in-mysql/
Yep - that’s the guide we’re using. Nice work :)