Limiting ntopng disk usage
-
Curious how others are handling this.
I've got a 8192 MB RAM Disk for /var to prevent a ton of writes to my drive, which feels pretty generous, almost excessive.
I've got notpng configured as such:
Regardless every couple of days I'm managing to overflow /var, and thus pfsense goes down hard.
I really hate the idea of setting up influxdb in a VM on another box for this, is it possible to just segregate ntopng to something less critical than /var/? Ideally any package would not be writing to a shared RAM disk which could take down the entire system.
-
@digitalgimpus ntopng writes a ton of data to disk. There is no way around this. To lessen it a bit, you could turn off the host time series data, and the interface data. But there will still be a ton of writes. Even if you use InfluxDB off host for the traffic data, there will still be a lot of local writes via Redis. In short, if you care about disk writes, do not run ntopng.
FWIW, I recommend ntopng be used as a diagnostic resource when you have issues. I do not recommend ntopng as something you continuously run.
-
@dennypage Noted, and thanks.
