Filesystem Architecture Request (RRD specifically)

[Rael]

All the RRD files are created and stored in one central directory. When you have 1000 targets you can easily generate over 100,000 rrd's.

This makes 'ls' useless and dramatically decreases cacti performance.

Wouldn't it make alot more sense to segregate the rrd's by target name?

IE:

./rra/<hostname>/x.rrd

[hgd26]

All the RRD files are created and stored in one central directory. When you have 1000 targets you can easily generate over 100,000 rrd's.

This makes 'ls' useless and dramatically decreases cacti performance.

Wouldn't it make alot more sense to segregate the rrd's by target name?

IE:

./rra/<hostname>/x.rrd

Use this Patch: "Structured RRD Path"

http://forums.cacti.net/viewtopic.php?t=15025

[Rael]

Good link, thanks.

This however is a enthusiast provided patch and not a developer supported feature of Cacti.

I don't want to apply a patch to find out later I'm unable to upgrade my Cacti instance.

When does the Cacti development team plan to support this feature and implement it into the product?

I was actually surprised to find out you stored rrd's in this manner, when storing them according to targetID seems like such a no brainer.