4 ms·

It looks cool but it's not actually any more usable than just a table / gridview list... Consider :- 1. A list can quickly be filtered to show only critical s

by smiler 16y ago

It looks cool but it's not actually any more usable than just a table / gridview list... Consider :- 1. A list can quickly be filtered to show only critical state servers - I probably don't care about servers which aren't doing anything 2. If I want to look for a specific server - I have no idea which one it is - I have to click to find it. A grid means I can look for it instantly 3. The info being displayed takes a while to digest as to what I'm seeing on the 3d axes with regards to ping etc... A grid just gives me the numbers and I can read them quickly. Yet again a use of pretty graphics where it really isn't needed

pquerna 16y ago
there is a gridview inside cloudkick, this is just an alternative view on the data, for example this is the dashboard: https://www.cloudkick.com/site_media/images/home_tour/dashboard.png https://www.cloudkick.com/site_media/images/home_tour/dashbo... There is also the /monitoring/ page (which i don't have a screenshot of handy), which is a grid view similar to what you are talking about.
polvi 16y ago
We do pretty exactly what you described on the monitoring overview -- except for the filter in #1. Great feedback, however, and we will look at including that! This is a very different take on visualizing your infrastructure. I encourage you to setup your servers and post on the big screen at your office. After watching it for awhile, you will start to be able to see when something is an anomaly just with a glance.
tripngroove 16y ago
Disclaimer: I work at Cloudkick. Imagine looking at a list of 500 servers and trying to determine how their aggregate memory usage was trending in real-time. To quickly address your concerns: 1. Servers that are critical turn red and blink - there's no need to filter anything since your eyes have already done it. 2. This tool isn't really designed to be a gateway to arbitrary servers; it's showing you anomalies, problems, and aggregate trending. 3. I think this could be a fair point, but with only 3 (clearly labeled) axes, I think it's hard to suggest that the learning curve for digestion the information is incredibly steep. If you actually think how it's set up at the moment is too confusing, I'd love to hear suggestions. We leave this up on the big screen at the office and it makes it very easy to tell when something untoward is happening with our servers, without really having to devote direct attention to the visualization. We designed it so problems stand out and make themselves known to you. One of our guiding principles is to move quickly and take user feedback though, so if you've got any constructive criticism, let's keep the discussion going!!!

by smiler 16y ago

pquerna 16y ago

there is a gridview inside cloudkick, this is just an alternative view on the data, for example this is the dashboard: https://www.cloudkick.com/site_media/images/home_tour/dashboard.png https://www.cloudkick.com/site_media/images/home_tour/dashbo... There is also the /monitoring/ page (which i don't have a screenshot of handy), which is a grid view similar to what you are talking about.

polvi 16y ago

We do pretty exactly what you described on the monitoring overview -- except for the filter in #1. Great feedback, however, and we will look at including that! This is a very different take on visualizing your infrastructure. I encourage you to setup your servers and post on the big screen at your office. After watching it for awhile, you will start to be able to see when something is an anomaly just with a glance.

tripngroove 16y ago

Disclaimer: I work at Cloudkick. Imagine looking at a list of 500 servers and trying to determine how their aggregate memory usage was trending in real-time. To quickly address your concerns: 1. Servers that are critical turn red and blink - there's no need to filter anything since your eyes have already done it. 2. This tool isn't really designed to be a gateway to arbitrary servers; it's showing you anomalies, problems, and aggregate trending. 3. I think this could be a fair point, but with only 3 (clearly labeled) axes, I think it's hard to suggest that the learning curve for digestion the information is incredibly steep. If you actually think how it's set up at the moment is too confusing, I'd love to hear suggestions. We leave this up on the big screen at the office and it makes it very easy to tell when something untoward is happening with our servers, without really having to devote direct attention to the visualization. We designed it so problems stand out and make themselves known to you. One of our guiding principles is to move quickly and take user feedback though, so if you've got any constructive criticism, let's keep the discussion going!!!