Testing Needed: New Traffic Graphs (widget and page)
-
Right now the text on the right shows me pulling 10 meg which is correct. The graph to the left shows me at 1 meg. I assume this is a known issue?
Appears to be a difference between bits and bytes.
-
The new widget seems to be handling readings wrong.
The 'old' one did read out an speedtest with a stable red line around 118Mbit/s here on the dashboard. The new one, seems to be jumping up and down between 50 and 200Mbit/s. (200Mbits/?!) Maybe the average is correct, but its hard to make a useful readout. (See attached picture - Should be a strait line in the red bubble)(I know that some of these are already known or explained…)
Interface names wrong.
Widget will not 'messeure / remember' if jumping out of the webpage and back in again.
Possibility to change line-colors (Red for upload and blue for download or something)
Possibility to change Mbyte to Mbit in bandwidth page./Michael.
-
Possibility to change line-colors (Red for upload and blue for download or something)
Why red? red in a firewall is for alerts (should be), top is in bottom is out no worries. If it were one upon another then is diferent story. I like the colors if stays one in top and other on bottom but i prefer one on upon other with transparency and different color (no red) for better spacing and more detail.
-
The 'System Information' widget have red indicators as well. And they are not alerts.
It does not necessary have to be red, just the possibility to change the colors. Now they are blue and light-blue, and I think the colors are to close to each other.
-
any clue when you plan on bumping this to mainly the bits vs bytes ?
-
Just click on the wrench in the title bar, select bits or bytes and save ;-)
Nice job BTW!!
-
That is only in widget on page Status/Traffic Graph you don't have nothing to chose, is in Bytes and the info (right pane) in in bites(?!!).
-
the new Traffic Graphs very beautiful , however , and too bad the fact that when we change the tab and turn it resets .
-
it also seems to reset on its own without changing tabs was monitoring traffic during apple event and every so often it would reset
miss the number at the top -
I replaced the traffic graphs with d3.js (similar to the other recent graph changes) since the old traffic graphs hadn't been touched in ages and had their limitations.
Note: There was a CSS change that effects the Status > Monitoring and Traffic Totals graphs, and those changes may not make it in the build until tomorrow. So if graphs look funny (smaller than usual) that is likely the issue.
Known Issues:
1. There is sometimes a missing datapoint when the graph starts. I still need to figure out how to clean that up, but it doesn't break anything.
2. I plan on showing latest in/out traffic in the upper section
3. I need to default to bits and not bytes
4. the widget isn't honoring the naming of interfaces [fix pending]
Hi jdillard,
would it be possible to use MM-DD date format in the graph?https://forum.pfsense.org/index.php?topic=117523.msg652703#msg652703
-
The missing Interface Names are irritating… Any Chance ?
-
any way to give the user the ability to change the defaults? For instance I like mine to default to interface:LAN, Display:hostname. Trivial to change every time I open it, but if I could I would like to change the default.
Also can we leave the names up for longer, or even better have a rolling average for the say top 5? Assuming it would be difficult, but a further enhancement I see in our meraki devices would be to point to a listed hostname, and then see the traffic graph for it as an individual over-layed.
-
There was no answer to this thread, but another topic was opened regarding Traffic Graph.
Maybe someone could merge the threads ?And.. could we revert Back to old Traffic Graph if it is impossible to fix the problems using d3.js ?
-
The missing Interface Names are irritating… Any Chance ?
I think this one alone proof that nobody is working on this or they change direction in the graph technology.
-
@jdillard is the one who has done the work on this so far not sure where he is at in updates hope this gets cleaned up before 2.4 release
