One of the changes I made as part of making the FireBrick use SVG graphs was that the speed traces changed from "+" points on each 100 second sample to a line graph. SVG make this way easier and it was sort of what I always wanted, but PNG pixel based would have been messy.
Old PNG style :-
New SVG style :-
I like the line graphs. I feel they show more, and work well. Importantly, if there is a short period of no traffic or even high traffic, that transition is not clear on the old graphs.
However, there are cases where it looks more "cluttered" and can mask some of the data usually at the bottom of the graph showing latency.
Oddly, quite a few people do not like it, and I had a long conversation with one person that felt it was "wrong" to draw lines. He felt we added data points that did not exist. But a speed graph on a car would have lines even though sampled for periods to make speed from pulses. Eventually he could not explain why lines were wrong. I don't think they are "wrong", just a different way to show the speed and how it changes over time.
Now, I agree, aesthetically they are different, and they have pros and cons.
So latest code aims at a compromise, the "+" marks and thinner lines :-
I am not sure of that. It works OK. So maybe just the "+" marks on SVG?
My conclusion, we need options! The latest code makes SVG which has all points so can work with markers on the line or not, and so we end up with SVG that can be controlled by CSS after the fact. This means we can have user settings on our control pages for A&A, and we have settings for default CSS controls on the FireBrick code. This should allow users (and staff) a choice. Because of change freeze this won't apply until new year, then we will look in to what options we offer. FireBrick users that have access to alpha builds can play now.
I never knew it could be so controversial!
P.S. Plan is now to make code use lines only but CSS controllable so A&A control pages could have options in the new year.