Tag Info

New answers tagged


Another alternative - one that gets rid of the discontinuity at midnight (or 10am) - would be a spiral visualization, with one day per circuit. Here's a picture of a spiral visualisation from an earlier UX answer of mine: You could use 24 hours per circuit, and show history over 7 or 10 days easily. The same time of day always shows at the same angle, ...


I agree with Charles; the same chart but with the axes reversed makes more sense to me. I tend to think of time in terms of timelines, which your chart just isn't doing for me right now. I also think you want some way to indicate continuities within broken time chunks, so it's clear that the kid didn't wake up briefly at midnight. download bmml source ...


Well, I was struggling with this problem. I don't recommend to use log scale, first not all users will understand this scale, second one, if you have values that are close the difference between them won't be noticeable on the graph. I recommend two solutions: break graphs: but we need to remember to change the scale, scale must be adjusted not to the ...


To me, the labels in both zoom levels of your original example look to small. It's possible that simply having a larger fixed label size will solve the problem. If that isn't adequate, then you will have to do some kind of scaling, whereby the labels increase as you zoom in, but at a less than linear rate. This is do-able, but will be a bit tricky to get ...


Google deprecated the whole Image Charts API, which allowed for the rendering of sparklines and many other visualizations. It was not specifically aimed at removing sparklines alone. The API was part of a larger group of "old" APIs that were deprecated at the same time. Based on this context, it seems to be an engineering decision.


UptimeRobot is a tool for monitoring server downtimes (I'm just a user, no other connection whatsoever). They're showing a small graph on the left side for the up-/downtimes for every watched server in the last 24 hours (I edited the image because none of my watched servers had a downtime in this period). If you click on one of the bars, you see details on ...


This is the way Pingdom chose to visualize it in their Public Status Pages: (Disclosure: I was the front-end web developer who implemented this graph back in 2010, but not the designer or originator of the concept.)


I have seen the following visualization used to represent down time and it has been effective: The illustration in the question requires too much thinking. The linear time line works well for a 24 hour timespan.


An aside: COTS stands for Commercial Off The Shelf. Per the chart - it tells me nothing. Both the X and Y axis are so deep I have to following an enormous gulf in order to guess that the server was down roughly in the timeframe of 20:24-20:28. Why are there 4 lines in-between the hour lines when they only jump by 2 hours? My eye also has to wander a great ...

Top 50 recent answers are included