NEW Monitoring graph
-
Hmm this doesn`2t look right.
I intentionally selected IPsec iface as in last 8 hours there was 0 traffic.
Green line seems to be left over from quality graph.
I checked with multiple browsers, same behaviour.yes when changing rrd type or interface it, sometimes, it keeps the lines of the previous graph.
-
Hi all!
Latest package fixed my issue.
Thanks! -
I might have to redo that for after 2.3 and can include the auto-update and multi-option stuff you worked on at that point.
There has got to be a better way that reuses more of the code…
Thanks for the setting expectations update. I've been and still am using both the auto updating and quick links and love them.
P.S. With draw from scratch the graph type works now. So may want to enable bar graph selection.
No problem. Thanks for all the help! Seriously.
The code has been a little volatile, but I think it is about to settle down. I see moving a lot of repetitive code to functions (but that shouldn't really effect future additions much) and also adding an update bit to the draw_function that skips over code on an update (just an idea at this point). Just trying to keep the code maintainable so we can keep adding to it without the complexity killing us.
-
yes when changing rrd type or interface it, sometimes, it keeps the lines of the previous graph.
This is fixed now: https://forum.pfsense.org/index.php?topic=107790.msg605180#msg605180
-
After the latest monitoring rev I notice that if the graph is refreshed while a tool-tip is displayed that the tool-tip becomes permanent. Moving the mouse/pointer back over the graph will still bring up a new tool-tip display but the not remove the previous one.
Just pushed an update that fixes this. thanks for catching/reporting it!
-
@virgiliomi:
…but try running the following instead of editing:
sort -u -o /usr/local/etc/php/extensions.ini /usr/local/etc/php/extensions.ini
Yeah, there's nothing to sort in an empty file… :)
Unless one of those filenames should be something else? :)
Edit: Or, unless you were referring to sorting AFTER updating? Couldn't tell...
After talking with Garga we aren't quite sure what happened as it seems to have only affected a few people I would make the fix (fill in the file) and upgrade normally after. That problem seems to have hit at a certain snapshot and not come up since, so hopefully whatever caused the issue is behind us.
-
I've also seen the call to undefined function fetch_rrd() a few times over the past couple of weeks.
In my case it has only happened after a "crash" on second reboot after update.Steps:
- Update (auto reboots and all is fine).
- Console option 6 (shutdown).
- Create VM snapshot.
- Boot pfSense - something goes awry and screen messages scroll for a few seconds like disk clean up from ungraceful shutdown. System auto reboots fine but then fetch_rrd() call issue occurs.
I've never tried to trouble shoot cause. Just restore previous VM snapshot and re-update.
-
for the last two builds i cant get the graphs to show
where the graph is to show i get a red box with "Error: SyntaxError: Unexpected token F"
and in the logs i get
Crash report details:
PHP Errors:
[26-Mar-2016 02:16:58 Etc/GMT-7] PHP Fatal error: Call to undefined function rrd_fetch() in /usr/local/www/rrd_fetch_json.php on line 130 -
for the last two builds i cant get the graphs to show
where the graph is to show i get a red box with "Error: SyntaxError: Unexpected token F"
and in the logs i get
Crash report details:
PHP Errors:
[26-Mar-2016 02:16:58 Etc/GMT-7] PHP Fatal error: Call to undefined function rrd_fetch() in /usr/local/www/rrd_fetch_json.php on line 130I am on
2.3-BETA (amd64)
built on Sat Mar 26 19:54:12 CDT 2016
FreeBSD 10.3-RELEASEstill same problem does no one else have this?
-
still same problem does no one else have this?
Follow the directions in this post, then I'd reboot to make sure PHP is all clean. If you're not a console editor type, you can use Diagnostics > Edit File to edit the file in question (it'll likely be blank). Paste in the code from that post, then save the file and reboot.
-
for the last two builds i cant get the graphs to show
where the graph is to show i get a red box with "Error: SyntaxError: Unexpected token F"
and in the logs i get
Crash report details:
PHP Errors:
[26-Mar-2016 02:16:58 Etc/GMT-7] PHP Fatal error: Call to undefined function rrd_fetch() in /usr/local/www/rrd_fetch_json.php on line 130I am on
2.3-BETA (amd64)
built on Sat Mar 26 19:54:12 CDT 2016
FreeBSD 10.3-RELEASEstill same problem does no one else have this?
I created a redmine ticket that summarizes the information from this thread:
https://redmine.pfsense.org/issues/6041
If you have anything to add I would do it there as to keep the information in one place.
edit: Garga thinks he already found a fix (talk about fast!): https://github.com/pfsense/pfsense/commit/475f0b6dbd9d93e96e58b4b54870c9aa760e99f7
-
I created a redmine ticket that summarizes the information from this thread:
https://redmine.pfsense.org/issues/6041
If you have anything to add I would do it there as to keep the information in one place.
edit: Garga thinks he already found a fix (talk about fast!): https://github.com/pfsense/pfsense/commit/475f0b6dbd9d93e96e58b4b54870c9aa760e99f7
If you want to test this now you can do a git sync and then option #16 in console (Restart PHP-FPM). Otherwise you can wait to upgrade to the next snapshot and the install/reboot process will take care of it.
If you are still running up against this issue, your feedback on this fix is greatly appreciated.
-
for the last two builds i cant get the graphs to show
where the graph is to show i get a red box with "Error: SyntaxError: Unexpected token F"
and in the logs i get
Crash report details:
PHP Errors:
[26-Mar-2016 02:16:58 Etc/GMT-7] PHP Fatal error: Call to undefined function rrd_fetch() in /usr/local/www/rrd_fetch_json.php on line 130I am on
2.3-BETA (amd64)
built on Sat Mar 26 19:54:12 CDT 2016
FreeBSD 10.3-RELEASEstill same problem does no one else have this?
I created a redmine ticket that summarizes the information from this thread:
https://redmine.pfsense.org/issues/6041
If you have anything to add I would do it there as to keep the information in one place.
edit: Garga thinks he already found a fix (talk about fast!): https://github.com/pfsense/pfsense/commit/475f0b6dbd9d93e96e58b4b54870c9aa760e99f7
oh nice thanks guys, i was just confused as i seen people talking about the graphs and i couldn't see them :)
-
Are they working for you now?
-
What is required to get the new dark graphs on the 2.3 beta? Mine are still white.
-
Apparently goes to 2.3.1. Monitoring took a lot of time so no time for the graph. I search for the topic where this is discus but don'r find it.
-
What is required to get the new dark graphs on the 2.3 beta? Mine are still white.
If you are referring to traffic graphs that is 2.3.1. Otherwise you can change the theme in System > General Setup.
-
Monitoring graphs are looking GREAT! I see you fixed the problem with quality graphs, where packet loss (%) and delay (ms) was on the same axis and caused the graph to be poorly readable. Now it is brilliant! Well done guys! Two thumbs up!
-
Please forgive me if this has been asked, I must be particularly dense today because i've been unable to locate any way to easily see the total amount of data in megabytes or gigabytes that has passed through an interface for a specific amount of time?
-
Please forgive me if this has been asked, I must be particularly dense today because i've been unable to locate any way to easily see the total amount of data in megabytes or gigabytes that has passed through an interface for a specific amount of time?
Unfortunately, this was lost with the move away from the static RRD graph images to the more dynamic graph format.
I believe the only way to do this now would be to use an add-on package. At the moment, the only two network monitoring packages available are RRD Summary (provides data use over the past month using the same RRD data the graphs use) and DarkStat (a little more advanced, watching the amounts of data that individual hosts are transferring).
None of the other network monitoring packages have been converted to the new format for 2.3 yet.