speaking of sql partitioning - i've seen "handmade" solutions in mysql versions prior to 5.1 (watch4net APG - EMC SMARTS frontend), but I had no interest in it, because when you run "transporter" on 8 cpu machine with 16Gb's or ram and 250 days uptime - you simply do not care of how big your heap-table is and how many "slow queries" it produces
adopting the plugin for "mortal" users requires some time, currently I don't have it (at least until end of 2008). And, if we'll proceed with complete rrdtool replacement (otherwise i do not see any reasons why we should need endless partitioned sql storage) - this plugin should contain sub-plugin - "rrdtool emulator" - that's a challenge you know
ps: we had some tests a while ago - ~2500 DSL customers whose snr's, iptv/internet traffic and errors/discards were monitored during the weekend. 3 days of pooling every 1min resulted in ~60Gb "transporter" sql table. Of course plugin is far not perfect and there are many ways to optimize it, but stillt's more complicated that it might seem.
Very nice, I have been wanting to do something like this for a while. However, you may want to implement some form of partitioning to allow the data to be pruned rapidly. Since MySQL does not currently support partitioning (5.0 anyway), you might want to consider a workaround, or we should start to look at MySQL 5.1 to resolve table size and management issues.
I will likely be adding this type of functionality to the base, but for now, this is your domain