This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[atlas] Updated RIPE Atlas roadmap
- Previous message (by thread): [atlas] Updated RIPE Atlas roadmap
- Next message (by thread): [atlas] Updated RIPE Atlas roadmap
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
dave
gboonie at gmail.com
Thu Dec 19 21:25:06 CET 2013
Hi Philip, Working via API is not something anyone can do. Also, it seem to me to be something for a measurement which was given quite some thought. The web UI allows novice users to do a quick test as a tool for faultfinding. No API knowledge needed. That is what I'm using Atlas for. Quick short tests from multiple points. Thanks for your response. > Op 19 dec. 2013 om 19:34 heeft Philip Homburg <philip.homburg at ripe.net> het volgende geschreven: > >> On 2013/12/19 19:26 , dave wrote: >> Also, I'd love to have constrains for probe selection. This would allow >> to ping from i.e. 3 probes in each AS. Please consider such a feature. > > Just thinking out loud, is this something that should be part of the web > UI? Before you know it, probe selection becomes some sort of complex > filter language that can do anything, but nobody knows how to use it. > > Instead, it may be worth doing these kinds of things through the API: > download the complete list of probes, apply your filter criteria and > then create a measurement that involves the probes that match.
- Previous message (by thread): [atlas] Updated RIPE Atlas roadmap
- Next message (by thread): [atlas] Updated RIPE Atlas roadmap
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]