Bug #9807
closedPackets Monitoring graphs are being incorrectly scaled
100%
Description
It looks like the data used for the packets logging is being incorrectly multiplied by 8 as though it is assuming a Bytes value that shouldn't be be applied to PPS.
Whilst running an iperf3 test the monitoring graphs show a pps value of 644.22 kpps but the switch port logs a 5s average of 80600 pps for the same connection.
Tested against:
2.5.0-DEVELOPMENT (amd64) built on Sat Sep 28 22:21:52 EDT 2019 FreeBSD 12.0-RELEASE-p10
Also seen here in 2.4.4p3: https://forum.netgate.com/topic/147011/pfsense-monitoring-graphs
Files
Updated by Viktor Gurov almost 5 years ago
- File rrd_fetch_json.php rrd_fetch_json.php added
for some reason there is no rrd_fetch_json.php and status_monitoring.php files on github
fixed version:
... case "inpass": if ($settings['category'] === "traffic") { $multiplier = 8; } $ninetyfifth = true; $format = "s"; break; case "max": $format = "s"; break; case "inpass6": if ($settings['category'] === "traffic") { $multiplier = 8; } $ninetyfifth = true; $format = "s"; break; case "outpass": if ($settings['category'] === "traffic") { $multiplier = 8; } $invert = $invert_graph; $ninetyfifth = true; $format = "s"; break; case "outpass6": if ($settings['category'] === "traffic") { $multiplier = 8; } $invert = $invert_graph; $ninetyfifth = true; $format = "s"; ...
Updated by Jim Pingle almost 5 years ago
- Project changed from pfSense to pfSense Packages
- Category changed from RRD Graphs to Status_Monitoring
They are a part of the Status_Monitoring package (which is included in the base install), so the files are in the freebsd-ports repo under sysutils/pfSense-Status_Monitoring
Updated by Viktor Gurov almost 5 years ago
Updated by Jim Pingle almost 5 years ago
- Status changed from New to Pull Request Review
Updated by Renato Botelho almost 5 years ago
- Status changed from Pull Request Review to Feedback
- Assignee set to Renato Botelho
- % Done changed from 0 to 100
PR has been merged. Thanks!
Updated by Jim Pingle almost 5 years ago
- Target version changed from 2.5.0 to 2.4.5
This was picked back to 2.4.5 as well, so needs testing there.
Updated by Viktor Gurov almost 5 years ago
- Status changed from Feedback to Resolved
tested on pfSense 2.4.5.a.20191220.1407
works,
Resolved