Some suggestions for stat.ripe.net
Hi! I think that this is a great project! It has a nice interface and is very useful to get an "one page" info for everything. Excelent work! I have a few sugestions for the new system that I think can improve the value of this project: * Add an input field for each box, so the owner of the resource (or maybe anyone, I haven't think this too hard) can add more info about that particular item (ie: on geolocation, add the "true" location, on assignments within allocation - well, it's obvious :-P) * On the visibility test, when you get a "!" and a porcentage (let's say, 80%) it would be great to know if there was 80% of the probes over there that wasn't able to "see" the resource, or if 80% of the time was not visible, or if 80% of the times failed to check. Anyhow, I think it would be great to know more about this topic. If something failed, the hour of the fail, or the route to get to that resource. * Can you add a new box for do some kind of lookinglass over the resource from different locations/peers? that would be awesome! When i have to test some anycast cloud, i have to fly all over the looking glass that i can find, and then do my own analysis. Kind regards, Mauricio -- Mauricio Vergara Ereche User #188365 counter.li.org DNS Admin NIC Chile mave [@] nic [.] cl Miraflores 222 piso 14, Santiago CHILE +56 2 9407710 Codigo Postal: 832-0198 http://www.nic.cl
Hi Mauricio, Thanks for your contribution! On 04/05/2011 14:39:08, Mauricio Vergara Ereche wrote:
I think that this is a great project! It has a nice interface and is very useful to get an "one page" info for everything. Excelent work!
I have a few sugestions for the new system that I think can improve the value of this project:
* Add an input field for each box, so the owner of the resource (or maybe anyone, I haven't think this too hard) can add more info about that particular item (ie: on geolocation, add the "true" location, on assignments within allocation - well, it's obvious :-P)
This is a nice idea, we'll need to think about if/how it could be done on a per plugin basis. If you (or anyone) have specific ideas for any plugin, let us know. Two (of several) considerations: 1) For most resource data, the RIPEstat output is taken from mirrored RIPE NCC sources. We can't update the original via RIPEstat. And in most cases, unless we can properly identify the true resource holder, we couldn't anyway 2) In the specific case of geolocation, this data is sourced from MaxMind, and we have no way of correcting it. We could perhaps store an offset... I realise you're probably not a RIPE NCC region resource holder, but those who are have the ability to check and edit location data for their own resources via our LIR Locator. Perhaps one day this data set will feed into the RIPEstat geolocation module: http://labs.ripe.net/Members/kranjbar/ripe-ncc-lir-locator/
* On the visibility test, when you get a "!" and a porcentage (let's say, 80%) it would be great to know if there was 80% of the probes over there that wasn't able to "see" the resource, or if 80% of the time was not visible, or if 80% of the times failed to check. Anyhow, I think it would be great to know more about this topic. If something failed, the hour of the fail, or the route to get to that resource.
The methodology text should make this clear - it's far too vague at present. We can work on that - it's on our todo list. What I'd like to hear from you and this list is what optional metrics you'd like us to use to calculate this figure? What is meaningful and useful to you? We can support multiple options, what would you find most interesting/useful?
* Can you add a new box for do some kind of lookinglass over the resource from different locations/peers? that would be awesome! When i have to test some anycast cloud, i have to fly all over the looking glass that i can find, and then do my own analysis.
If you join the RIPEstat demo on Tusday https://labs.ripe.net/Members/markd/ripestat-live-demo-5 and you might be in for a nice surprise :) All the best, Mark -- Mark Dranse RIPE NCC
* Can you add a new box for do some kind of lookinglass over the resource from different locations/peers? that would be awesome! When i have to test some anycast cloud, i have to fly all over the looking glass that i can find, and then do my own analysis.
Those of you who were at the closing plenary (or listening remotely) may have noticed that Mauricio won the prize for best RIPEstat suggestion. The looking-glass idea is the one that the judges really liked. It's one that provides some real-time information on resources, and aligns with the general goal of RIPEstat, to create a single portal for ops tools dealing with Internet resources. And as one of the judges put it, "I wanted something similar when I admin'ed DNS servers" :) Thanks to all who contributed ideas. There was a lot of debate among the judges about which to put first. And even though there was only one iPod, many more of the suggestions will get another prize (possibly better!) -- getting implemented in RIPEstat. So please keep the suggestions coming, and speak up about what you think of the other suggestions so far! Best, --Richard
participants (3)
-
Mark Dranse -
Mauricio Vergara Ereche -
Richard L. Barnes