Re: [atlas] Can I issue a traceroute measurement with multiple targets?
Thanks Robert, that's useful and a good insight on how built-in measurements are mapping sources and destinations. Best, Vasileios From: Robert Kisteleki Sent: Tuesday, February 11, 2020 8:45 AM To: Vasileios Giotsas ; ripe-atlas@ripe.net Subject: Re: [atlas] Can I issue a traceroute measurement with multiple targets? Hello, Our definition of "measurement" is "one or more probes, one target" so seemingly the answer is "no". However, a target can be a host name that is resolved on the probe, which provides a workaround: if the name resolves to different addresses, the measurement will in effect run against different targets. Each result carries the target IP so in effect your desired result can be achieved. The so called "topology measurements" (see https://atlas.ripe.net/docs/built-in/) are implemented this way: the names topology[46].dyndns.atlas.ripe.net resolve to a different address almost each time. The code behind this service is open source (see https://github.com/RIPE-NCC/atlas-dyndns) so you can relatively easily set it up for your own needs. We also have the means of serving other names in this domain if you have a fixed list of targets. So far there has not been enough demand to implement a self-service API for this. Note that our current implementation does not take into account which probe is asking, so in case of multiple probes involved there is only a certain statistical probability for all probes measuring all targets; there's no guarantee that a full source-target mesh is achieved. Regards, Robert On 2020-02-10 23:38, Vasileios Giotsas wrote: > If I have 100 IPs to target from a single probe, is it possible to > create a single measurement with 100 targets similar to how I'd do if I > wanted to target a single IP from 100 probes? > I've read through the Atlas API documentation and couldn't find anything > like that but it looks like some of the built-in measurements do that. > > Thanks, > Vasilis
[atlas] Can I issue a traceroute measurement with multiple targets?
If I have 100 IPs to target from a single probe, is it possible to create a single measurement with 100 targets similar to how I'd do if I wanted to target a single IP from 100 probes? I've read through the Atlas API documentation and couldn't find anything like that but it looks like some of the built-in measurements do that. Thanks, Vasilis
[atlas] Time difference between results and update of measurement status
I've seen that the status of a measurement is updated much later than when the measurement results become available. For instance, while the RTTs of a ping measurement are returned the status is still Ongoing for up to 3 minutes. Is there anything (such as sanity checks) that intervenes between the update of the results and and update of the measurement status, which may change the results? Or is it safe to assume that once the results are out the measurement status will eventually change to 'Stopped', just a bit later? Thanks! Vasileios
Re: [atlas] Meta-information dumps for built-in measurements?
Thanks Robert, With that opportunity just some feedback on the API: it's generally very convenient, my only issue is that for repeated measurements (not one-off) it's not easy to get the queries that have been executed in a certain time frame. You have to parse the results from the start of the measurement and get those executed between the desired time frame by checking its result separately, which is slow (at least I haven't found a better way!) So having some sort of metadata dumps makes it faster to go through the queries that have been executed in a certain period. I guess another alternative is to download the traces dumps but here the bottleneck is the download time even for a period of 1 day. Best, Vasileios From: Robert Kisteleki Sent: Tuesday, September 4, 2018 7:28 AM To: Vasileios Giotsas Cc: ripe-atlas@ripe.net Subject: Re: [atlas] Meta-information dumps for built-in measurements? On 2018-09-04 03:16, Vasileios Giotsas wrote: > Is there any repository > like https://ftp.ripe.net/ripe/atlas/measurements/ that contains > meta-information about built-in RIPE Atlas measurements (the above > repository contains meta-information only for public measurements)? > > I couldn't find anything similar in the new FTP repository > at https://data-store.ripe.net/datasets/atlas-daily-dumps/ > > I guess using the API is an alternative but it would be more convenient > to have such dumps > > Thanks, > Vasileios Hello, https://atlas.ripe.net/api/v2/measurements/?id__lte=100 is a pretty good approximation of what you're after. Built-ins change very rarely, so a one-time query will give you virtually everything about built-ins. Note that the above mentioned full dump of measurement metadata via FTP is not sustainable (in its current form it's growing endlessly) so we'll highly likely to change this in the near future. Regards, Robert
[atlas] Meta-information dumps for built-in measurements?
Is there any repository like https://ftp.ripe.net/ripe/atlas/measurements/ that contains meta-information about built-in RIPE Atlas measurements (the above repository contains meta-information only for public measurements)? I couldn't find anything similar in the new FTP repository at https://data-store.ripe.net/datasets/atlas-daily-dumps/ I guess using the API is an alternative but it would be more convenient to have such dumps Thanks, Vasileios
[atlas] No suitable probes error, and inconsistency between results and measurement status
Hi all, I have a number of traceroute measurements that end-up with status "No suitable probes". The documentation explains that this error is quite rare, the quote below is from https://atlas.ripe.net/docs/udm/ "No suitable probes: The measurement cannot currently be executed as defined due to a lack of available probes. This may be because you asked to use probes that don't exist (for example, probes in an AS in which there are no probes) or because all of the probes you requested were too busy to take on new jobs. This latter scenario is very rare however." In my case happens in all of my latest measurement request that ask for different probes. It also happens when I use the wizard in the web interface which selects the probes automatically. Even weirder, some of these measurements appear to have been completed when I check the API. For instance, measurement 12244352 has status 6 (No suitable probes), and the web interface doesn't show any results. But the API endpoint shows that it has been executed and returned results: https://atlas.ripe.net/api/v2/measurements/12244352/ I'd appreciate some pointers on how to resolve this issue. Thanks, Vasileios
