NEW Monitoring graph

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.

![Quality End Zero.jpg](/public/imported_attachments/1/Quality End Zero.jpg)
![Quality End Zero.jpg_thumb](/public/imported_attachments/1/Quality End Zero.jpg_thumb)

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.

![Change to Defaults.jpg](/public/imported_attachments/1/Change to Defaults.jpg)
![Change to Defaults.jpg_thumb](/public/imported_attachments/1/Change to Defaults.jpg_thumb)

Clown

Thanks, Monitoring works now.

There should be some rounding of the values, see the attached Picture.

Edit:
This happens just when the 'Timer period' is greater than 1day.

monitoring_floats.PNG_thumb

Harvy66

@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?

Should probably add a "*" and have a note of something like "*all reported values are aggregated over a rolling window". "Min" and "Max" are a bit deceiving when they'er averages themselves. Not in a bad way, but in a non-intuitive way that can cause confusion with some datasets.

samoth

Any reason why my graphs wouldn't have any data? No matter what I pick in settings, I get 0 for values in the graph.

2016-03-06_140325.png_thumb

grandrivers

packet loss should be red in color

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.

Makes for nice smooth lines that look pretty for consumer class. Ideally a granularity selector based on the RRD data granularity of the selected graph time period would be nice.

Thanks.

xbipin

i have a full install where monitoring graphs work but i have another nanobsd but monitoring shows blank graphs there, is there some way to enable it because on this nanobsd install i never previously enabled RRD graphs

jdillard

@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".

So "delay" should be "avg delay" and "stddev of delay" should just be "stddev"?

jdillard

@grandrivers:

packet loss should be red in color

manually assigning colors is a bad idea for this use case. Possibly in the future, more specialized charts could get special treatment.

dennypage

I think this would be sufficiently clear.

@jdillard:

So "delay" should be "avg delay" and "stddev of delay" should just be "stddev"?

jdillard

@Clown:

Thanks, Monitoring works now.

There should be some rounding of the values, see the attached Picture.

Edit:
This happens just when the 'Timer period' is greater than 1day.

Not sure how this never happened to me, but should be fixed next time around.

maverick_slo

Hi!

I`m on latest snap.
See attached image. I have some packet loss (intentionally) and now graph is useless to me.
Can sth be done in this way?

I can`t see any useable data from graph…

graph_new.png_thumb

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.

Makes for nice smooth lines that look pretty for consumer class. Ideally a granularity selector based on the RRD data granularity of the selected graph time period would be nice.

Thanks.

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

See attached image.

Granularity.jpg_thumb

NOYB

@dennypage:

I think this would be sufficiently clear.

@jdillard:

So "delay" should be "avg delay" and "stddev of delay" should just be "stddev"?

Yes that would differently be better. Here's another labeling possibility. What about this:
delay average
delay std. dev.

Just throwing it out there to be considered.

NOYB

Bubble values not matching graph.

![Values Not Match Graph.jpg](/public/imported_attachments/1/Values Not Match Graph.jpg)
![Values Not Match Graph.jpg_thumb](/public/imported_attachments/1/Values Not Match Graph.jpg_thumb)

jdillard

@NOYB:

Bubble values not matching graph.

Are you on the latest version? I added a few lines to change the rounding location if the number was under .001 (could probably be done more elegantly, I'm working on cleaning some of the SI/rounding stuff up).

I'm also checking out your patch, but looks good at first glance.

NOYB

To paraphrase Richard Dawson.

pkg info says… pfSense-Status_Monitoring-0.6

Dashboard says..
2.3-BETA (i386)
built on Sun Mar 06 08:37:58 CST 2016

What is the latest?

NOYB

@samoth:

Any reason why my graphs wouldn't have any data? No matter what I pick in settings, I get 0 for values in the graph.

Try removing "inpass total" and "outpass total". That's what works for me.

NOYB

@jdillard:

@NOYB:

Bubble values not matching graph.

I added a few lines to change the rounding location if the number was under .001 (could probably be done more elegantly, I'm working on cleaning some of the SI/rounding stuff up).

Think the delay and std. dev. values should be converted to milliseconds and for values less than 1 ms to microseconds. And include the units designation ms or us.

@jdillard:

I'm also checking out your patch, but looks good at first glance.

Thanks. I like it. Any idea how to clear the lines/bars of a previous graph so that changing between line and bar doesn't create an overlay?