Hello, We've added some changes to the UI yesterday. From now on upon registering a new probe, or changing its attributes (from the probe status page) the host can set the following additional information: * Router type: optional, describes the router/NAT model you have, mainly in a home installation. This information could be useful for us to correlate weird probe behavior across similar router models. * Allowed bandwidth: it's not used yet, but you can imagine the future purpose for it :) * DNS options: this has been asked by some of you before. By default it's off. If you set it to "simple" then your probe will have a probe-xxxx.probes.atlas.ripe.net DNS entry. If you set it to "obfuscated" then your probe will have a <something random looking>.probes.atlas.ripe.net DNS entry. We'll activate this feature soon. * Public: you can make your probe visible to everyone, which means that all Atlas users will see the probe in their probe list (with role "Viewer"), and they will be able to see the measurement details on the probe status page. Consider this an experimental feature -- we have to see if it's useful or not. You'll need to reload the page (with the browser "reload") in order to see these changes. Regards, Robert
Robert Kisteleki wrote:
Hello,
We've added some changes to the UI yesterday. From now on upon registering a new probe, or changing its attributes (from the probe status page) the host can set the following additional information:
* Router type: optional, describes the router/NAT model you have, mainly in a home installation. This information could be useful for us to correlate weird probe behavior across similar router models.
Great idea!
* Allowed bandwidth: it's not used yet, but you can imagine the future purpose for it :)
:-)
* DNS options: this has been asked by some of you before. By default it's off. If you set it to "simple" then your probe will have a probe-xxxx.probes.atlas.ripe.net DNS entry. If you set it to "obfuscated" then your probe will have a <something random looking>.probes.atlas.ripe.net DNS entry. We'll activate this feature soon.
* Public: you can make your probe visible to everyone, which means that all Atlas users will see the probe in their probe list (with role "Viewer"), and they will be able to see the measurement details on the probe status page. Consider this an experimental feature -- we have to see if it's useful or not.
Well, I'll take a short break before I set the tick-mark for public :-) I think it is a nice idea, too, with 2 minor caveats: - the probes with type host should remain at the top of the list (the sort function for the column seem to not being available yet), and - rather than "public", or as an alternative, I would prefer to enable known users to beceome "viewers" and even be allowed to change configuration. This would be very helpful for en environment like ours, where there's more than one host for our probes. Right now both these numbers are *very* small :-), but if this develops into the structure I'd like to see, it will no longer be easy...
You'll need to reload the page (with the browser "reload") in order to see these changes.
Regards, Robert
Thanks a lot, Wilfried.
* Public: you can make your probe visible to everyone, which means that all Atlas users will see the probe in their probe list (with role "Viewer"), and they will be able to see the measurement details on the probe status page. Consider this an experimental feature -- we have to see if it's useful or not.
This is a nice option, but putting all the public probes in the "My Probes" window makes things a little cluttered. Perhaps you could make a separate "Public Probes" tab? --Richard
Strong +1, couldn't spot my probes amongst all other my-probes Joao On 12 Jan 2011, at 16:25, Richard L. Barnes wrote:
* Public: you can make your probe visible to everyone, which means that all Atlas users will see the probe in their probe list (with role "Viewer"), and they will be able to see the measurement details on the probe status page. Consider this an experimental feature -- we have to see if it's useful or not.
This is a nice option, but putting all the public probes in the "My Probes" window makes things a little cluttered. Perhaps you could make a separate "Public Probes" tab?
--Richard
-----Original Message----- From: ripe-atlas-admin@ripe.net [mailto:ripe-atlas-admin@ripe.net] On Behalf Of João Damas Sent: 12 January 2011 15:27 To: Richard L. Barnes Cc: Robert Kisteleki; ripe-atlas@ripe.net Subject: Re: [atlas]Some new UI features
Strong +1, couldn't spot my probes amongst all other my-probes
Joao
On 12 Jan 2011, at 16:25, Richard L. Barnes wrote:
* Public: you can make your probe visible to everyone, which means that all Atlas users will see the probe in their probe list (with role "Viewer"), and they will be able to see the measurement details on the probe status
You can click on the Roles column and set the filter to 'host'. That removes all the public probes. It seems to remember it between login sessions too. Rick Hodger Senior ICT Administrator Bytel T/AS Atlas-Communications Ltd. page.
Consider this an experimental feature -- we have to see if it's useful or not.
This is a nice option, but putting all the public probes in the "My Probes" window makes things a little cluttered. Perhaps you could make a separate "Public Probes" tab?
--Richard
OK, we'll think about something, but in the meantime the 'Role' column is your friend -- it's easy to spot the outlier there, and you can also filter to "Host". Robert On 2011.01.12. 16:26, João Damas wrote:
Strong +1, couldn't spot my probes amongst all other my-probes
Joao
On 12 Jan 2011, at 16:25, Richard L. Barnes wrote:
* Public: you can make your probe visible to everyone, which means that all Atlas users will see the probe in their probe list (with role "Viewer"), and they will be able to see the measurement details on the probe status page. Consider this an experimental feature -- we have to see if it's useful or not.
This is a nice option, but putting all the public probes in the "My Probes" window makes things a little cluttered. Perhaps you could make a separate "Public Probes" tab?
--Richard
Robert Kisteleki wrote: Another entry for the wish-list: :-)
* Public: you can make your probe visible to everyone, which means that all Atlas users will see the probe in their probe list (with role "Viewer"),
and it would be cool to have those probes tagged, which are IPv6 rnabled! Thanks, Wilfried. PS: and please add a segment for labs.ripe.net over IPv6!
Hi, On 01/12/2011 10:22 AM, Robert Kisteleki wrote:
Hello, [...] * Public: you can make your probe visible to everyone, which means that all Atlas users will see the probe in their probe list (with role "Viewer"), and they will be able to see the measurement details on the probe status page. Consider this an experimental feature -- we have to see if it's useful or not.
I see that some people put uplink details in the description field (as did I...). However since this is a text field the information is rather chaotic. I think we need a select box for this information, dsl, cable, 10 GE fibre to the home, neutrino transmission... No, I don't have an exhaustive list to put in the select box, if something like that isn't readily available maybe we can do a poll on this list. Wilfried suggested to have a tag for IPv6 enabled probes, maybe we can also track the kind of IPv6 connectivity (none, tunnelled, native)
Regards, Robert
Thanks, Florian -- I remember yesterday, but the memory is in my head now. Was yesterday real? Or is it only the memory that is real?
Hi, I'd like to suggest the AS number for the list columns (could be determined automatically), and also a search box (id, description, location, asn) might come in handy if the list of public probes continues to grow. I guess sorting by geo /distance/ to the viewer's location (which could be manually configured or just set to some probe's location, e.g. an own probe) would be very helpful as well, as I often like to compare how things look like from "somewhere completely else". Thanks! - D.
participants (7)
-
Dennis Koegel -
Florian Obser -
João Damas -
Richard L. Barnes -
Rick Hodger -
Robert Kisteleki -
Wilfried Woeber, UniVie/ACOnet