NEW Monitoring graph

[grandrivers]

i have a data set that doesn't seem to play well with current setup if it would help like for quality also seems like traffic is much much lower.
I am trying not to be critical but this is a bit like 2 steps forward 1 step backwards or maybe 1.75 steps backward


[NOYB]

@grandrivers:

i have a data set that doesn't seem to play well with current setup if it would help like for quality also seems like traffic is much much lower.
I am trying not to be critical but this is a bit like 2 steps forward 1 step backwards or maybe 1.75 steps backward

The good news is that it does appear to be a work still in progress.  Encourage you to keep commenting on what does and doesn't work well.

[jdillard]

@grandrivers:

i have a data set that doesn't seem to play well with current setup if it would help like for quality

not sure what that means.

@grandrivers:

also seems like traffic is much much lower.

It was pulling bytes not bits. This is fixed (along with a lot of other things) and will be updated tomorrow.

[MikeV7896]

@NOYB:

@NOYB:

Could we have more granularity than 5 minutes please?  Especially on the 1 hour graph.
The RRD has 60 data points an hour but the graph seem to display a granularity of only 12 data points per hour.

Pull request submitted for this:
https://github.com/pfsense/FreeBSD-ports/pull/73

Still hoping to see this resolution selector make it in at some point… though I understand that when looking at certain large timeframes, it would be necessary to force the resolution to something lower, it would be nice to have high resolution as an option at least at the 1 and 8 hour timeframes.

[jdillard]

I just pushed some fixes and bumped the version, the builder will pick them up next time around.

Things I fixed (and remembered):

• Inpass/Outpass Total timeline errors on i386 (integer overflow, yay!)

• Improved Summary units (could be improved further, but a big step in customization)

• Added reset RRD data option

• Added ability to turn on/off RRD Graphing option

• Added NOYB's PR with resolution options (pretty sweet)

• Changed bytes to bits so traffic should be more accurate

• Rounded the y axes to 2 decimal places

• Fixed the rounding in the tooltip if under .01 so it doesn't show as 0

Coming soon: Option to save current settings as defaults.

[whitexp]

Interactive Graph
Error: SyntaxError: Unexpected token F

[grandrivers]

0.7 monitoring much better , current bugs
delay should be in ms not S
not sure why it has -500 ms listed


[jdillard]

@grandrivers:

0.7 monitoring much better , current bugs
delay should be in ms not S
not sure why it has -500 ms listed

I think I can get that closer. After I get the defaults working, I'll circle back around.

That is the same as .5. Axis units still need some customization work, they are all SI formatted now.

[jdillard]

@whitexp:

Interactive Graph
Error: SyntaxError: Unexpected token F

Did you just upgrade? Are you on 64 or 32bit? What graphs do you have selected?

In Chrome right click the screen and click Inspect. Then choose the Network tab and refresh the browser. Click the update button on the WebGUI and then you should see a line item with rrd_fetch_json.php at the bottom of the dev tools window. If you click that then choose the response tab within it you should see what the server responded with. Are there any errors in there?

[grandrivers]

" they are all SI formatted now."  i dont know if I understand and am a sure at this point it looks harder for most (isp's) i like to have proof of poor service

dhcp leases graph is missing will that be worked on at some point

[whitexp]

see

[jdillard]

@grandrivers:

" they are all SI formatted now."  i dont know if I understand and am a sure at this point it looks harder for most (isp's) i like to have proof of poor service

dhcp leases graph is missing will that be worked on at some point

It auto converts to the SI prefixes: http://www.shimadzu.com/an/hplc/support/n9j25k000000y4ah-img/n9j25k000000y8nb.jpg

It is just tricky in this case because there are a lot of different use cases sharing the same graph, it'll get there.

DHCP leases (DHCP category) shows up for me. I assume you have it enabled?

[NOYB]

Submitted a few more pull requests last night.

1. Auto update.
   Updates the graph 4 times per selected resolution.
   Updates the graph on settings change.
   https://github.com/pfsense/FreeBSD-ports/pull/77

2. Collapsible and configurable show/hide settings panel.
   Same as status system logs filter and manage log panels.
   Replaced the "Update" button with refresh icon on title bar.
   I think this would be real nice combined with being able to set a default view.  Open the monitor and have your preferred view without the settings panel consuming a third of the display.  A cleaner look.
   https://github.com/pfsense/FreeBSD-ports/pull/78

3. Use same units in tooltip as graph on quality.
   Code wise a bit of a hack I think and I'm sure Dillard and/or others can do it much more elegantly.  But it suffices for me for now.  We mere humans just don't relate well to long strings of digits.
   https://github.com/pfsense/FreeBSD-ports/pull/79

See attached image of my current incarnation.

[grandrivers]

you are correct its disabled and wont enable ,my bad ill try to chase that down

[jdillard]

I'm guessing the labels across the bottom are in the next PR ;)

I'll make comments for each of the PRs on github.

[heper]

@grandrivers:

you are correct its disabled and wont enable ,my bad ill try to chase that down

i just tried to enable the dhcp graphs on a previously disabled interface. they showed right up.

goto https://your_pf_ip/status.php & search for <statsgraph>it should show something like```
<statsgraph>yes</statsgraph>

[grandrivers]

i goto dhcp server tick Enable RRD statistics graphs hit save page reloads with it unticked

[heper]

best to start a new thread for that. i've just tried this on 2 systems and enable/disable works as intended.

[NOYB]

@jdillard:

I'm guessing the labels across the bottom are in the next PR ;)

I'll make comments for each of the PRs on github.

Yup.  Future graph meta data PR.  Maybe tonight.
Thanks.

[whitexp]

@jdillard:

@whitexp:

Interactive Graph
Error: SyntaxError: Unexpected token F

Did you just upgrade? Are you on 64 or 32bit? What graphs do you have selected?

In Chrome right click the screen and click Inspect. Then choose the Network tab and refresh the browser. Click the update button on the WebGUI and then you should see a line item with rrd_fetch_json.php at the bottom of the dev tools window. If you click that then choose the response tab within it you should see what the server responded with. Are there any errors in there?

Crash report begins.  Anonymous machine information:

amd64
10.3-RC1
FreeBSD 10.3-RC1 #446 22a5a00(RELENG_2_3): Thu Mar 10 07:19:29 CST 2016    root@pfs23-amd64-builder:/usr/home/pfsense/pfsense/tmp/obj/usr/home/pfsense/pfsense/tmp/FreeBSD-src/sys/pfSense

Crash report details:

PHP Errors:
[10-Mar-2016 15:07:02 America/Sao_Paulo] PHP Fatal error:  Call to undefined function rrd_fetch() in /usr/local/www/rrd_fetch_json.php on line 125
[10-Mar-2016 15:14:08 America/Sao_Paulo] PHP Fatal error:  Call to undefined function rrd_fetch() in /usr/local/www/rrd_fetch_json.php on line 125
[10-Mar-2016 16:45:11 America/Sao_Paulo] PHP Fatal error:  Call to undefined function rrd_fetch() in /usr/local/www/rrd_fetch_json.php on line 125