New Traffic Totals package available for testing
-
Is there any way it can save the last graph settings for each of the 4 output options?
Thanks
Myk -
Ah no, I forgot about that. I haven't figured out a good way to save config options for this package just yet. I'll take another look at that as well.
-
also
On the daily stats, can we have to option to reverse the order, newest on top - so you dont have to scroll to the bottom of the list. Thats the way the old vnstat2 did it.
Thanks again for this package!
Myk
-
Ah no, I forgot about that. I haven't figured out a good way to save config options for this package just yet. I'll take another look at that as well.
one of my docker containers, rutorrent front end, saves selected columns, width, columns sortings etc via a json file that is save - maybe that is a simple option
or maybe something on the user/browser side?
Thanks
Myk -
On the daily stats, can we have to option to reverse the order, newest on top - so you dont have to scroll to the bottom of the list.
I'll see about reversing the table order for all of them. Also, possibly making it a sortable table.
-
Installed 2.3.2 just for this… was going to try and wait until release, but now you did this. :)
So far in favor of all mentioned items... save default graph settings, sortable table, and most recent period at the top.
My comment is that it seems to be showing an average speed for the period rather than the actual amount of data. Maybe make that an option as well? Some people might care about the average speed for the period... but most are more interested in the actual amount of data transferred instead.
Additionally, it would be good to see vnstatd added to the Services widget on the dashboard, so we can make sure it's running and properly tracking traffic.
-
@virgiliomi:
My comment is that it seems to be showing an average speed for the period rather than the actual amount of data. Maybe make that an option as well? Some people might care about the average speed for the period… but most are more interested in the actual amount of data transferred instead.
What leads you to believe it is average? It should be totals.
@virgiliomi:
Additionally, it would be good to see vnstatd added to the Services widget on the dashboard, so we can make sure it's running and properly tracking traffic.
It uses a cron job not vnstatd, I thought it would be more reliable. You can see the cron job if you install the cron package. I also haven't added the functionality that lets you change how often the cron job runs yet.
-
@virgiliomi:
My comment is that it seems to be showing an average speed for the period rather than the actual amount of data. Maybe make that an option as well? Some people might care about the average speed for the period… but most are more interested in the actual amount of data transferred instead.
What leads you to believe it is average? It should be totals.
I've been watching a 5Mbps+ video stream for the past 45 minutes… yet for this hour (25 minutes so far), it's not showing anywhere near the amount of traffic showing it should be showing... Unless the numbers are really megabytes? The unit on the graph says "bits per second"... that's clearly not right.
-
I believe I have the units represented wrong, it looks like it should be KiB/MiB/etc. Thanks for catching that!
-
ya, mine shows today aprox 10mb, old graph shows right at 9.xg
Myk
-
Ok, that's what screwed me up then. :)
As for cron versus service… It's not a big deal to me either way... I just wasn't sure how it was running. I did quickly pick up that it was updating every 5 minutes though.
-
Also on the side of the graphs - Traffic (Bits per Second) - does not work - its total traffic - no speed
Myk
-
Yea, I think that was an artifact of using the Status > Monitoring as a starting point. I'll try and get some of these fixes in tomorrow.
-
Just wondering about why PHP is listed as a dependency for the package. Isn't PHP part of the whole pfSense ecosystem anyway? Or is that for future planning if it goes away? Does this potentially cause problems if PHP is upgraded by pfSense core, but the package isn't updated to reflect the new version of PHP, when someone goes to install the package?
-
It uses a cron job not vnstatd, I thought it would be more reliable.
Why is the vnstatd daemon unreliable on FreeBSD? Had it running for years on a Linux box with no problems at all.
-
It uses a cron job not vnstatd, I thought it would be more reliable.
Why is the vnstatd daemon unreliable on FreeBSD? Had it running for years on a Linux box with no problems at all.
He didn't say that it was unreliable on FreeBSD… just that he thought it would be more reliable as a cron job. Using the cron job, it's only running every 5 minutes rather than a constantly running process that could be stopped at any time leaving holes in the data.
I see pluses and minuses to both ways... I personally have no preference. I just want it to work and accurately track my usage. It doesn't need to be minute-by-minute... updating every 5 minutes is fine by me. Most of what I care about (and probably most people) is monthly usage more than anything.
-
Hmmm…
Is this topic about the new graphing system on 2.3 which replaced RRD? Or is it an addition to that? Or is it just a similar graphing to what's already built-in?
Why as a separate package? -
@virgiliomi:
He didn't say that it was unreliable on FreeBSD… just that he thought it would be more reliable as a cron job. Using the cron job, it's only running every 5 minutes rather than a constantly running process that could be stopped at any time leaving holes in the data.
Cron jobs are run by a daemon that could also be stopped at any time ;) So the question remains, why not use the vnstat daemon? Don't get me wrong, I just want to understand it, don't want to offend anyone :)
-
@virgiliomi:
Just wondering about why PHP is listed as a dependency for the package. Isn't PHP part of the whole pfSense ecosystem anyway? Or is that for future planning if it goes away? Does this potentially cause problems if PHP is upgraded by pfSense core, but the package isn't updated to reflect the new version of PHP, when someone goes to install the package?
I had a line in the Makefile that didn't need to be there. I'll be taking it out and it should remove the PHP dependancy.
-
It uses a cron job not vnstatd, I thought it would be more reliable.
Why is the vnstatd daemon unreliable on FreeBSD? Had it running for years on a Linux box with no problems at all.
It's not unreliable on FreeBSD, just harder to tie into all the necessary GUI bits last time I looked. Maybe I was looking at it wrong.
