Date: Fri, 22 Mar 2019 14:55:25 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 236716] net/ntopng: pfSense ntopng Port - Historical graph inaccurate Message-ID: <bug-236716-7788-QqGbwlMqhT@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-236716-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-236716-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D236716 Guido Falsi <madpilot@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|ports-bugs@FreeBSD.org |madpilot@FreeBSD.org Summary|pfSense ntopng Port - |net/ntopng: pfSense ntopng |Historical graph inaccurate |Port - Historical graph | |inaccurate CC| |madpilot@FreeBSD.org Status|New |Open --- Comment #1 from Guido Falsi <madpilot@FreeBSD.org> --- I'm taking this as the maintainer of the ntopng port. I'm not sure though how to address this. It looks like an ntopng problem, s= ince the graphs are generated by it. Does not look like a porting problem but an upstream bug. I'll try looking at it. Anyway it is important to note that historical data= is actually smoothed out, as you say, so a single peak, or many small peaks wi= ll rarely show in the graph. If I remember correctly those graphs are generated using rrdtool. That tool registers data for timeframes (let's say 5 minutes= , or 1 day) and for each timeframe registers a minimum a maximum and an average value. It can well be the graph is drawn using only the averages, while the other data also uses the min/max values, which then would never show in the graph. It could be interesting to test if this happens with a vanilla FreeBSD box = or a a Linux box too. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-236716-7788-QqGbwlMqhT>