Status: Monitoring is completely broken, pfSense 2.4.5

johnpoz

6 years is a lot of data for what type of data it is.. Does that really make sense to keep the data for that long?

I just looked and mine goes back to dec 2017.. I would assume when I fired up this 4860.. But when moved to new hardware I wouldn't be bringing that data over..

While its great info for sure, but I doubt the bug report would get much looking into until someone is sitting around twiddling their thumbs - hmm, hmm what to work on ;)

A quick fix I would think would just be to truncate rrd data at X.. So it only ever goes back so far, or so many specific data points..

But yeah @scurrier great work on tracking it down..

scurrier

There's a quick and easy version of a fix so maybe I will try to figure out which git branch to work from and submit a pull request on it that mimics the open heart surgery I did in the browser.

scurrier

Looks like I've been running this firewall since the end of 2014.

Interestingly, the data for some metrics doesn't go back as far as others. Compare these two. Note that the first one shows nulls for part of the data even though I know the firewall was running at that time. I wonder why.

Gertjan

@scurrier said in Status: Monitoring is completely broken, pfSense 2.4.5:

I wonder why.

Have a look at the the folder where rrd files are stored. Maybe you used another type of WAN interface before, like a pppoe access - or static setup. The rrd file will have another name for that period.

Btw : didn't know that that much data is stored in a rrd file :

mine goes back to 2014 also.
The file that was just before that time was based on a pppoe access, I wiped that stale rrd file long time ago.

edit :
IPv6 since 2014 also :

The big chunck was the period I tried to sync my Syno NAS with some Microsoft Office cloud over night. I'll try that again when fiber gets invented.

kiokoman

strange, but i don't have that lines on my php,
the one you mentioned here
https://forum.netgate.com/post/925667

maybe it's not up to date?

serbus

Hello!

Just winging it here...I dont have a rrd dataset to reproduce the problem or test any solutions...

It looks like most (all?) rrd's are setup to hold 2284 days (6.25yr) of data. Once hit, the consolidation strategy must push the resolution out to 7200sec (?).

You could always increase the max. Is 10 years enough? Maybe 12years? There would need to be special update scripts to "resize GROW" all the current data. Yuk!

Maybe just add any possible resolutions to timelookup? What if rrd starts using one that wasnt added?

The simplest solution might be to just convert the timeformat assignment to a ternary operator, like :

var timeFormat = (timeLookup.hasOwnProperty([data[0].step]) ? timeLookup[data[0].step] : "%Y-%m-%d");

Maybe you could backup/zip/post your rrd data set so others could load/test possible solutions?

It is pretty cool that pfsense has the durability/longevity to run into this sort of problem :).

John