Hi,
Is it possible to create multiple data retention profiles?
For example - I want to store high resolution traffic info for router links for a long time, but I only care about the last week of server ping response time.
At the moment I’ve got everything on high resolution which wastes space and creates unnecessary load.
Thanks.
Hello,
no these are the only options I’m aware of.
Hi,
Thanks for the quick response.
The cleanup options don’t really help in keeping the RRD filesize low because the RRD files are created to their full size at device-addition time. So while the cleanup may zero out data from within the RRD file, the filesize won’t reduce.
We’re trying to keep high resolution for the important stuff like uplinks, etc. But there’s not many of these. On the other hand there’s tons of less important stuff for which the resolution and data retention times are not important 
Oh well, looks like some sacrifice needs to be made here across the board - either diskspace+performance or resolution.
Regards.
I disabled sensors from graphing which saved me a ton of space and load.
if you want to try it i believe it was $config['sensors'] = false; if i remember correctly
I disabled sensors from graphing which saved me a ton of space and load.
Thanks for that, good tip!
Here’s the line:$config['poller_modules']['sensors'] = true;
I see there’s also a selective option:
// Sensors $config['allow_entity_sensor']['amperes'] = 1; $config['allow_entity_sensor']['celsius'] = 1; $config['allow_entity_sensor']['dBm'] = 1; $config['allow_entity_sensor']['voltsDC'] = 1; $config['allow_entity_sensor']['voltsAC'] = 1; $config['allow_entity_sensor']['watts'] = 1; $config['allow_entity_sensor']['truthvalue'] = 1; $config['allow_entity_sensor']['specialEnum'] = 1;
The data retention is set when the RRD is created.
So you could set your desired RRA in your config.php, delete the files you want to have the different retention and run the poller to create the files, then remove your RRA config to set it back to default for new files.
Ha! You’re on to something. I like !
Definitely gives me what I want, even though it’s a bit of overhead to change the files manually.
BTW - do you know if the change to config.php applies immediately after save (for new RRD I create), or whether I need to restart services which will cause holes in the graphs?
Regards.
Honestly, it doesn’t gain you much. RRD files are pretty efficient storage wise.
LibreNMS does not have persistent processes, so yes, config.php always applies right away.
Your suggestion does gain me a lot - 3 years storage for important stuff, 1 week for not important stuff. There’s lots of servers we monitor and 1 week for them is enough. This will save tons of storage.
The immediate config.php application is good, means no restart services and traffic graph gaps.
Only 11GB of RRD for our over 400 devices… Seems like you might be saving 20%-40% of that? Seems like a lot of effort and pain for 3-5GB of savings.
1 minute polling, ping only, 3 year retention = 100.2Mb file. I really need only a week.
Full device visibility on a large switch = several hundred GB, even though I really want only a few ports at that resolution.
My calculation for our network shows inefficient storage = 4-9Tb , efficient storage = 500-1200Gb.
It’s not only the storage, it’s also the time it takes to run graphs, poll devices, etc.
1 minute polling for everything we own is too much.
I absolutely like the idea of multiple profiles, even if it means manual configs as suggested earlier.