 I've already given you a scenario where the id changes.

You named an edge case where one would

- delete a device
- add the same device
- wants all the old RRD data to be used despite the fact that there are 
gaps, maybe for a loooong time

 Another one would be when MySQL implodes and takes your database with it, or if MySQL updates happen to ruin your database in such a way that just clearing it and readding all of the devices makes sense.

That's actually the reason why storing those kind of data in the 
database makes much more sense. But I understand the limitations of RRD 
and the comfort it brings with it since it's an out of the box solution 
for all the graphs.

But that's still *not* a real reason since your backup should contain 
the potentially ruined database as well. Restore it and you are good.

 Naming device-specific directories by an arbitrary imaginary number instead of the very non-arbitrary hostname just because you think it's annoying the code changing hostname needs permission to write to the RRD folder is, well, stupid.

This might be your personal state but for sure not stupid. You may be 
aware that in your mysql database, you work with unique IDs as well and 
not with names. This is not only for performance reasons but because 
this is the only reliable and static item.

 I honestly do not understand how people who work in this industry can forward nonsensical ideas like this. This kind of thing is the exact opposite of the sort of principles that should be adhered to, maintaining high levels of simplicity and visibility and manageability.

Well that's your opinion. I'm sure there are others next to mine. But 
now I understand your thinking and your personality better so thank you 
for your opinion.

Jeff.

observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium