I'm working on creating some measurements and haven't quite moved into using the API yet and wanted to provide some feedback: 1) When creating a UDM, when it's scheduled but not yet assigned to probe(s), it would be nice to be able to increase the # of probes. 2) When creating a UDM and specifying source ASN, you can't type in that box and must use the pull-down. Related to #1, if you increase probes to (eg: 5) it resets to 1 after you select the ASN. 3) When stopping a UDM that is set for ongoing/no-end, it would be nice to have a 'stop now' vs having to pick the next 15 minute interval. In theory the system could auto-populate this. 4) I do like the probes/map/seismograph view, is it possible to provide a direct-link to these public UDMs without logging-in? (I haven't looked closely so there may be a way to do this). Trying to not need to fetch the data and generate my own graphs... 5) If I see a probe that is behaving poorly, eg: UDM 1665566 Probe# 3925, should I be providing feedback on this to others? I'm working on a Nx(N-1) measurement of these ASNs to determine which have persistent congestion that can be measured via RIPE Atlas if that is of interest to others. 174 209 701 1239 1299 2828 2914 3320 3257 3356 3491 3561 5511 6453 6461 7018 Those interested in this, I will be able to send you a list of UDMs to look at which are public. - Jared
On 17.05.2014 7:03 PM, Jared Mauch wrote:
4) I do like the probes/map/seismograph view, is it possible to provide a direct-link to these public UDMs without logging-in? (I haven't looked closely so there may be a way to do this). Trying to not need to fetch the data and generate my own graphs...
I would be interested in having this, too! Cheers, Tim
2) When creating a UDM and specifying source ASN, you can't type in
I'll answer the ones I can. that box and must use the pull-down. Related to #1, if you increase probes to (eg: 5) it resets to 1 after you select the ASN. We're currently working on a complete rewrite of the interface for UDM creation that will include all sorts of nifty things like autocompleting ASNs, so we've got you covered here.
3) When stopping a UDM that is set for ongoing/no-end, it would be nice to have a 'stop now' vs having to pick the next 15 minute interval. In theory the system could auto-populate this.
4) I do like the probes/map/seismograph view, is it possible to
Currently the only way to do this is to find your measurement in the list of measurements, right-click and select "Stop". In the new version you'll be able to stop a measurement on its detail page as well. provide a direct-link to these public UDMs without logging-in? (I haven't looked closely so there may be a way to do this). Trying to not need to fetch the data and generate my own graphs... Direct-linking is currently available through a convoluted URL structure that I'd rather not share publicly for fear that it will fall into common usage. The new pages (due out in the next few months) will follow the typical structure of /measurements/MEASUREMENT_ID/#tab-name, but that's not out yet. If you really can't wait for the new pages, email me off-list and I'll hook you up with the weird way we currently handle deep linking.
On May 19, 2014, at 6:22 AM, Daniel Quinn <dquinn@ripe.net> wrote:
Direct-linking is currently available through a convoluted URL structure that I'd rather not share publicly for fear that it will fall into common usage. The new pages (due out in the next few months) will follow the typical structure of /measurements/MEASUREMENT_ID/#tab-name, but that's not out yet.
If you really can't wait for the new pages, email me off-list and I'll hook you up with the weird way we currently handle deep linking.
Sure. Looking at this measurement: # 1665566 - 209->701 It seems to show that Qwest/Centurylink -> UUNet/VZ is “congested” and seeing queueing delay at some points of the day. Same for this one: # 1665596 - 701->2914 I’m going to go finish creating these measurements later today or tomorrow (time permitting). The general idea is something like: http://www.internetpulse.net/ But with atlas probes. - Jared
Hi,
I'm working on creating some measurements and haven't quite moved into using the API yet and wanted to provide some feedback:
Thanks, it's always appreciated!
1) When creating a UDM, when it's scheduled but not yet assigned to probe(s), it would be nice to be able to increase the # of probes.
This is somewhat tricky, because the answer is: it depends. If you schedule a measurement to be started in the future, then you can always just cancel the original one and schedule a new one. One can also change the set of probes for already running measurements, Although we don't recommend it because it can be very confusing when you interpret the results.
5) If I see a probe that is behaving poorly, eg: UDM 1665566 Probe# 3925, should I be providing feedback on this to others?
I believe that such bits of information could be useful. But, since they are one-to-one messages, it's probably not so useful to do them on this list :-) Would there be a need for an in-Atlas messaging service? If so, what should it allow / prevent? We have been thinking about such a thing before, but I would not want to pre-empt a useful discussion by exposing too much of our own ideas :-) Cheers, Robert
participants (4)
-
Daniel Quinn -
Jared Mauch -
Robert Kisteleki -
Tim Kleefass