The revision c7cb8b8e223580480426d586d017c9734a544971 for 1.12 contains what I suggested and much more.

1.12.2 is going to have a new feature called "post-install/upgrade tools". It contains a tool for JMX designed to fix all the existing JRBs/RRDs as well as the JMX data collection configuration files and graph templates.

Even if the tools have JUnit tests and were properly tested with real migrations, please create a full backup of your configuration file and JRBs/RRDs prior upgrade.

Thanks!

I agree, and it covers basically all possible corner cases by changing all non alphanumeric characters into "_" (which is used by the SnmpCollector).

I like the solution inside . I think that should be used instead of just adding \s to the conversion list.

I've added a very detailed procedure that expose the naming problem on for review.

Of course, all the ideas about the external tool to fix the names (based on my proposal), and any additional idea or use case that I'm missing will be very welcome.

This is going to fix one particular use case not all the use cases reported with the JMX collector for all possible combinations of RRD strategies.

My question for your solution is: what happen with the existing working JRBs/RRDs and all their combinations depending on storeByGroup ?

Here is why I'm asking:

On , I've provided a solution that fixes basically all possible problems, but requires to create an external tool to fix the current existing JRBs/RRDs to keep historic data. That's why I haven't committed the fix on our repo. On that issue (), I also attached the initial proposal for the JRB/RRD fix.

My fix also cover the following issues: , , , (this one), and

Actually, the proposal for the external tool also expose another problem: how to apply or execute post-install scripts to do non-db related stuff ? the JMX naming issue is one of them, the MAC on the SNMP Interfaces for 1.12 when upgrading from 1.10 is another use case.