switches STORAGE_TYPE on already existing DBs

[calestyo]

Hi Jörg.

I've just noted the following behaviour and maybe you can comment whether this is expected or not:

You recently mentioned, that RRD_STORAGE_TYPE is also just honoured on generation of the RRDs... I played a bit around and the following was the case:

a) RRD_STORAGE_TYPE was set to SINGLE and I already had a single RRD/XML for a given service. I then changed it to MULTIPLE (just in the config). "Nothing happened", and the single RRD continued to be upgraded... i.e. at first I had load.rrd/xml ... I changed to multiple... and I still only got load.rrd/xml

So far so good, I tried the other way round b) RRD_STORAGE_TYPE was set to MULTIPLE and I already had a single XML (load.xml) for a given service but multiple RRDs (load_load1.xml, load_load5.xml, load_load15.xml - no load.rrd). I then changed it back to SINGLE (just in the config). On the next sample update, a new single RRD (load.rrd) was created and used.

AFAIU you, this is not desired.

Cheers, Chris.

[lingej]

Hi Chris, you have to use rrd_convert to export your existing RRD files

http://docs.pnp4nagios.org/pnp-0.6/rrd_convert

[calestyo]

Based on our discussions via the phone, the long term goal is probably anyway to have MULTIPLE as the default. And as you said, right now it doesn't work, to globally have MULTIPLE and selectively SINGLE (which is I guess just the reason for the above issue ... or at least related).

Given that SINGLE is then likely "deprecated" anyway,... we can close this from my side. Thanks.