NEW Monitoring graph

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

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

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


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

[maverick_slo]

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

[jdillard]

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

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

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

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.


[maverick_slo]

Ummm see reply directly above your post…

[itsme01]

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

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]

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