NEW Monitoring graph
-
…(after the auto update is included)...
Will auto update reset the selected graphs as well?
(where is the selection done - probably directly in the browser, right?)If you mean will hidden series be restored, yes. It is no different than manually hitting the refresh button. It's just done for you at the selected a interval.
Well there is at least one difference. The loading graph banner isn't displayed.
-
So I haven't looked at the monitoring graph since I updated last night (and I'm not at home to look now)… has the last sample being 0 been fixed on the graphs yet? A couple of days ago I noticed that all lines still returned to 0 on the right side of the graph.
-
@virgiliomi:
So I haven't looked at the monitoring graph since I updated last night (and I'm not at home to look now)… has the last sample being 0 been fixed on the graphs yet? A couple of days ago I noticed that all lines still returned to 0 on the right side of the graph.
No.
Odds of having an RRD data point for the graph end time can be greatly increased though by updating/refreshing the graph near the end of the minute. Say like at hh:mm:59.
I committed a hack to the auto update pull request that syncs the refreshes to seconds 59 and it seems to work pretty well to prevent the graph from ending with values of zero (0). Once in a while it will if the RRD is updated between mm:59 and mm+1:00. Or the sync drifts off a bit and hits mm:00 once in a while.
But I think the real way to fix it is to use the most recent RRD data point time as the graph end time. And set graph start time to graph end time minus time period. Think something like that is how it works in previous version.
-
… option for multiple, adjustable graphs on the monitoring page ...
Though not multiple graphs, the quick links would make it real easy one click access to the same graphs you'd set up in your multiple graphs monitoring page. They just wouldn't be on the page at the same time. Unless you open multiple browsers or load them into a page with iframes. Think you could probably create an page that loads the monitoring page into multiple iframes. And if loaded with the correct post to select the quick link each iframe could auto load the desired graph.
-
So I updated to the latest snapshot last night, then again this morning… and now every time I visit the monitoring graph, I get this error:
Error: SyntaxError: Unexpected token F
The graph itself doesn't display, and no matter what I change the settings to, I can't shake that error.
Edit: Likely related… a crash report appeared when I went back to the dashboard, with the error...
[19-Mar-2016 08:40:26 America/New_York] PHP Fatal error: Call to undefined function rrd_fetch() in /usr/local/www/rrd_fetch_json.php on line 128
-
@virgiliomi:
So I updated to the latest snapshot last night, then again this morning… and now every time I visit the monitoring graph, I get this error:
Error: SyntaxError: Unexpected token F
The graph itself doesn't display, and no matter what I change the settings to, I can't shake that error.
Edit: Likely related… a crash report appeared when I went back to the dashboard, with the error...
[19-Mar-2016 08:40:26 America/New_York] PHP Fatal error: Call to undefined function rrd_fetch() in /usr/local/www/rrd_fetch_json.php on line 128
i have this problem about 1 week
-
Just thought I'd note… I updated tonight to the latest snapshot, which I saw included an updated status monitoring package, and the "SyntaxError: Unexpected token F" message still occurs. I just now submitted another crash report, in case it's needed...
-
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.
-
@virgiliomi:
Just thought I'd note… I updated tonight to the latest snapshot, which I saw included an updated status monitoring package, and the "SyntaxError: Unexpected token F" message still occurs. I just now submitted another crash report, in case it's needed...
This happened to me also. Although i couldn't find why, this is cause by /usr/local/etc/php/extensions.ini being empty. This is the content of the file where graph is workng :
extension=bcmath.so extension=bz2.so extension=ctype.so extension=curl.so extension=dom.so extension=filter.so extension=gettext.so extension=hash.so extension=json.so extension=ldap.so extension=mbstring.so extension=mcrypt.so extension=openssl.so extension=pcntl.so extension=pdo.so extension=pdo_sqlite.so extension=pfSense.so extension=posix.so extension=radius.so extension=readline.so extension=rrd.so extension=session.so extension=shmop.so extension=simplexml.so extension=sockets.so extension=sqlite3.so extension=ssh2.so extension=suhosin.so extension=sysvmsg.so extension=sysvsem.so extension=sysvshm.so extension=tokenizer.so extension=xml.so extension=xmlreader.so extension=xmlwriter.so extension=zlib.so extension=zmq.so zend_extension=/usr/local/lib/php/20131226/opcache.so zend_extension=/usr/local/lib/php/20131226/xdebug.so
I just edited the file with the above lines and this solved the problem. If you want you can give it a try.
-
@virgiliomi:
Just thought I'd note… I updated tonight to the latest snapshot, which I saw included an updated status monitoring package, and the "SyntaxError: Unexpected token F" message still occurs. I just now submitted another crash report, in case it's needed...
This happened to me also. Although i couldn't find why, this is cause by /usr/local/etc/php/extensions.ini being empty. This is the content of the file where graph is workng :
extension=bcmath.so extension=bz2.so extension=ctype.so extension=curl.so extension=dom.so extension=filter.so extension=gettext.so extension=hash.so extension=json.so extension=ldap.so extension=mbstring.so extension=mcrypt.so extension=openssl.so extension=pcntl.so extension=pdo.so extension=pdo_sqlite.so extension=pfSense.so extension=posix.so extension=radius.so extension=readline.so extension=rrd.so extension=session.so extension=shmop.so extension=simplexml.so extension=sockets.so extension=sqlite3.so extension=ssh2.so extension=suhosin.so extension=sysvmsg.so extension=sysvsem.so extension=sysvshm.so extension=tokenizer.so extension=xml.so extension=xmlreader.so extension=xmlwriter.so extension=zlib.so extension=zmq.so zend_extension=/usr/local/lib/php/20131226/opcache.so zend_extension=/usr/local/lib/php/20131226/xdebug.so
I just edited the file with the above lines and this solved the problem. If you want you can give it a try.
it solve the problem .. thanks
I believe the devs need to find out coz this file becomes empty after a few updates.
-
it solve the problem .. thanks
I believe the devs need to find out coz this file becomes empty after a few updates.
I'll bring this to garga's attention and get back to you. Thanks for looking into it!
edit: Garga says he pushed a change that should fix it, but try running the following instead of editing:
sort -u -o /usr/local/etc/php/extensions.ini /usr/local/etc/php/extensions.ini
-
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.Did you have a graph selected before going back to none on the right axis? I haven't figured out a fix for that yet…
-
Yup, thats the case.
Default I have 2 wans quality then I change to traffic and remove right axis… -
Yup, thats the case.
Default I have 2 wans quality then I change to traffic and remove right axis…I just changed it to draw the graphs from scratch every time and it fixed this issue (and also got rid of a bunch of duplicate code). Everything should behave the same, but you may want to double check everything.
-
…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...
-
I somehow missed the empty part of the post :-[
Let me get back with Garga, he set up that part.
-
Yup, thats the case.
Default I have 2 wans quality then I change to traffic and remove right axis…I just changed it to draw the graphs from scratch every time and it fixed this issue (and also got rid of a bunch of duplicate code). Everything should behave the same, but you may want to double check everything.
Would be nice if the draw_graph function had an option to "redraw" instead. Seems that draw from scratch should only be needed if the graph options have changed. That way updating same graph would be smoother, and probably more efficient too.
-
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…
-
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.
-
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.
-
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.