Percona Monitoring doesn't work well on Cacti 1.X.X

[jsarmento]

Hi guys,

Following the creation of issue Cacti/cacti#890 on cacti repo regarding some errors with Percona Monitoring Plugins, one of the developers did an audit of the Percona templates and presented his conclusions:

• Running those pmp-* commands on a Cacti 1.x system would not be advised without Percona doing some updates first as they are not compatible with Cacti 1.x.
• Cacti no longer supports the rra table for example. So, running all those commands will likely, at a minimum, result in errors.
• Please point them to the install_template.php file in the cli directory. I think the best router to get this template to Cacti 1.x is to import it into a 0.8.x version. Then export the various Device Templates. Those templates can be imported into Cacti 1.x using the import_template.php file. They should avoid all their Database magic and leave it to the Cacti API.

I believe that Percona Monitoring Plugins are excellent and maybe some of you can help out with this and the Cacti/cacti#890 issue.

[cigamit]

I have published the percona monitoring templates version 1.1.7 for Cacti 1.x at http://docs.cacti.net/templates for the time being. In order to do this, I had to install a Cacti 0.8.x instance, then install the monitoring templates. Then use Cacti's yet unpublished 'Package' plugin to put a bow on it.

I would suggest that in the future, once the Cacti Group publishes the Package plugin, that Perecona publish their packages for Cacti this way. There is a Cacti CLI script called 'import_package.php' that can be used to import these packages via the command line.

[netniV]

Any chance I can test out that plugin for my own projects?

[cigamit]

I have to remove our private key for signing and add a cli to create your own. Once that is done, I don't see any reason not too. The team has already agreed to it's release. It's just a timing thing and some small database edits to register trusted keys from others at this point. Maybe a day or two's work. It was not on my overtime schedule, but let me see what I can do.