NEW Monitoring graph

NOYB · Mar 7, 2016, 8:31 PM

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.

NOYB · Mar 7, 2016, 8:40 PM

@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 · Mar 7, 2016, 9:22 PM

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 · Mar 7, 2016, 9:53 PM

@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 · Mar 7, 2016, 10:29 PM

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 · Mar 8, 2016, 8:35 AM

@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 · Mar 8, 2016, 1:03 PM

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

maverick_slo · Mar 8, 2016, 12:49 PM

And another awesome thing would be to be able to select values yourself.
kbit, mbit etc…

jdillard · Mar 8, 2016, 3:00 PM

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

I am have some sample data to fix this issue. Hope to have a fix by the end of the day.

jdillard · Mar 8, 2016, 4:05 PM

@NOYB:

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

I am thinking the D3 .remove() function and/or feeding it an empty dataset. I'd have to play around with it.

jdillard · Mar 8, 2016, 9:39 PM

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

Not sure what sth means in this context. You can click the packet loss line in the legend to hide it so you can see the other lines.

itsme01 · Mar 9, 2016, 11:55 AM

There is still an issue with the Quality Graphs. If you have packet loss, the entire graph gets unreadable (see image below) as most of the graph is used to show the packet loss rather than the delay. Furthermore, packet loss is also shown strangely in the table below the graph.

![Screen Shot 2016-03-09 at 12.52.17.png](/public/imported_attachments/1/Screen Shot 2016-03-09 at 12.52.17.png)
![Screen Shot 2016-03-09 at 12.52.17.png_thumb](/public/imported_attachments/1/Screen Shot 2016-03-09 at 12.52.17.png_thumb)

maverick_slo · Mar 9, 2016, 12:12 PM

Ummm see reply directly above your post…

itsme01 · Mar 9, 2016, 12:23 PM

@maverick_slo:

Ummm see reply directly above your post…

Yes, I know. But just hiding a problem does not solve the problem, if you know what I mean. :P

I guess a solution to the problem would be to have packet loss on a secondary axis as it is in percent compared to the delay axis which is in ms/us.

Raul Ramos · Mar 9, 2016, 12:51 PM

A long solution should be a personalized and saved graph with custom name to do a single click and show our graph with respective data.

grandrivers · Mar 10, 2016, 1:13 AM

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

![Screen Shot 2016-03-09 at 8.12.38 PM.png](/public/imported_attachments/1/Screen Shot 2016-03-09 at 8.12.38 PM.png)
![Screen Shot 2016-03-09 at 8.12.38 PM.png_thumb](/public/imported_attachments/1/Screen Shot 2016-03-09 at 8.12.38 PM.png_thumb)

NOYB · Mar 10, 2016, 2:09 AM

@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 · Mar 10, 2016, 2:27 AM

@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 · Mar 10, 2016, 1:53 PM

@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 · Mar 10, 2016, 5:41 PM

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.