NEW Monitoring graph

[Raul Ramos]

@grandrivers:

black font is hard to read in dark theme

Black font? for the grid a less dar grey than the graph background not the light grey, for the name of the category and graph text should be the base text color or second base or whatever if for some reason they decide to go with a more buttonised approach. But some black text are in the switches and labels on the graph, to much dark yes, i agree.

[jdillard]

@grandrivers:

black font is hard to read in dark theme

I had it working for a while, but something happened with the CSS, I plan on looking into it today.

[jdillard]

I added the NTP, DHCP, Captive Portal, and Traffic Shaping graphs. I also made some of the interfaces friendly, still working on the VPN interfaces though.

I also forgot to take some troubleshooting code out, so depending on how soon you upgrade you might see it at the top  :-\

edit: Next version will also be showing VPN Users and friendly names for the OpenVPN servers.

[Clown]

Have an issue with that, until I established an OpenVPN-Interface the Monitoring looked good.

Afterwards please look at the attached Picture.

I could reproduse it on two Systems.

[jdillard]

See one post above…I was looking at it for so long I forgot it was there.

@jdillard:

I also forgot to take some troubleshooting code out, so depending on how soon you upgrade you might see it at the top  :-\

It won't be in the next snapshot though.

And speaking of OpenVPN interfaces, I am cleaning up their names in the dropdown now.

edit: I just bumped the version so the next one will also be showing VPN Users and friendly names for the OpenVPN servers. (as well as remove the stuff at the top)

[jdillard]

@jdillard:

@grandrivers:

black font is hard to read in dark theme

I had it working for a while, but something happened with the CSS, I plan on looking into it today.

There was a missing bracket in the CSS. I just pushed the fix.

[heper]

Version 	2.3-BETA (i386)
built on Fri Mar 04 10:20:14 CST 2016
FreeBSD 10.3-RC1 

Warning: Invalid argument supplied for foreach() in /usr/local/www/status_monitoring.php on line 150 Call Stack: 0.0004 118996 1\. {main}() /usr/local/www/status_monitoring.php:0 Warning: Invalid argument supplied for foreach() in /usr/local/www/status_monitoring.php on line 124 Call Stack: 0.0004 118996 1\. {main}() /usr/local/www/status_monitoring.php:0 Warning: Invalid argument supplied for foreach() in /usr/local/www/status_monitoring.php on line 200 Call Stack: 0.0004 118996 1\. {main}() /usr/local/www/status_monitoring.php:0 

[jdillard]

Arg, …so many test cases...so many VMs. Thanks heper! I think I just need to throw in some if statements for the openvpn stuff.

[NOYB]

Min: 0%
Avg: 1%
Max: 0%
See attached image.

I must have been daydreaming when that was being covered.  Could someone please tutor me before the test.

[jdillard]

@NOYB:

Min: 0%
Avg: 1%
Max: 0%
See attached image.

I must have been daydreaming when that was being covered.  Could someone please tutor me before the test.

I forget why we decided to put that code in, but I just took it back out.

[NOYB]

I must have been daydreaming again when this was being covered too.  Could some please tutor me before the test?
How can the standard deviation be greater than the maximum value of the data set?

Probe Interval: 15000 (15 seconds)
Alert Interval: 15000 (15 seconds)
All others default

dpinger output:

loss: 0, delay: .0095890, stddev: .0079330
loss: 0, delay: .0091930, stddev: .0081340
loss: 0, delay: .0092940, stddev: .0080790
loss: 0, delay: .0097080, stddev: .0078550
loss: 0, delay: .1656320, stddev: .2779040
loss: 0, delay: .1651380, stddev: .2781920
loss: 0, delay: .1653530, stddev: .2780680
loss: 0, delay: .1652700, stddev: .2781160
loss: 0, delay: .0046320, stddev: .0013230
loss: 0, delay: .0055140, stddev: .0006520
loss: 0, delay: .0056070, stddev: .0007150
loss: 0, delay: .0052770, stddev: .0008860

Also see attached quality graph image.

2.3-BETA (i386)
built on Fri Mar 04 19:46:06 CST 2016


[jahonix]

I have a Nano install on a retired ALIX for testing 2.3
Problem is that I don't see any RRD graphs there (no menu entry to select), is that correct? I'm on a built from Feb 4th.
The old traffic graphs in the dashboard are still there, though.

[MikeV7896]

@jahonix:

I have a Nano install on a retired ALIX for testing 2.3
Problem is that I don't see any RRD graphs there (no menu entry to select), is that correct? I'm on a built from Feb 4th.
The old traffic graphs in the dashboard are still there, though.

Correct, the RRD graphs have been replaced with this new monitoring graph (Status menu > Monitoring). This graph is more dynamic, lets you turn off elements you don't want, and also allows you to show two sets of data at once. (compare interfaces, look at more data for one interface, etc.).

RRD is still collecting the data that is presented in this new graph, but it's not generating the images anymore.

[jahonix]

Thanks, even I found it now.
Was looking at "System" for "Monitoring", not at "Status" …

[biggsy]

WRT to NOYB's screenshot above, the units on some of the graphs and tables are a bit . . . strange.

[jahonix]

A) Is there a plan to convert the dashboard traffic graphs to the new "Interactive Graphs" as well?

B) two horizontal grids are "a bit" hard to work with. There should only be one grid at a time, scaling the axis accordingly. (see screenshot)

C) Black as text color was already mentioned not being perfect. Maybe we can have the grid in black to get better contrasts. Currently the white grid is the dominant color, making it harder than necessary to read the graphs itself.
The color scheme in NOYB's screenshot is OK, I'm probably just seeing a CSS issue.


[dennypage]

The delay number isn't the maximum value of the set, it is the mean average of the set. Dpinger reports average and standard deviation values against the entire set the same way ping does in its summary.

Standard deviation is the square root of the variance, which is based upon squares of the offset from the mean. Use of squares means that the result can be higher than the mean.You can read the lengthy discussion of standard deviation on Wikipedia, or you can use one of the on-line calculators to experiment.

Here is one that spells stuff out: http://www.mathsisfun.com/data/standard-deviation-calculator.html

Put "2,2,2,2,2,20" for the numbers and start experimenting from there.

Sorry about the cuteness of the page :)

@NOYB:

How can the standard deviation be greater than the maximum value of the data set?

[NOYB]

Yes I know std dev can be greater than the mean.  Because of the graph/table labels it seems to indicate that it is greater than the max.

So the graph/data table "delay" label is not very accurate.
Delay is really average delay.  Thus in the data table the min, avg, max, columns actually contain min avg delay, avg avg delay, max avg delay.

Labeling the std dev row as "stddev of delay" seems to indicate that it is the std dev of the row labeled "delay".  Which would be more accurately labeled "avg of delay".

[NOYB]

Sometimes the quality graph ends with zero.  I know this was corrected a while back but sometimes it still happens.

Kind of makes the minimum column useless.


[NOYB]

Changed to all default settings from:
Probe Interval: 15000
Alert Interval: 15000
All others default

And this was the result.  See attached image.

But running dpinger -f at command line reports std dev consistently between 700 and 800 microseconds.  Which is consistent with the gateways widget reporting.