[atlas] Making a bunch of tests/measurements to a single destination is 'tedious'
- Previous message (by thread): [atlas] Making a bunch of tests/measurements to a single destination is 'tedious'
- Next message (by thread): [atlas] Making a bunch of tests/measurements to a single destination is 'tedious'
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Shane Kerr
shane at time-travellers.org
Thu Jan 24 09:52:38 CET 2019
Chris, On 24/01/2019 06.39, Christopher Morrow wrote: > howdy! > So, if I have a dns server somewhere and I want to make a bunch of > measurements: > "how does NYC see my dns?" (pick N probes near NYC) > "How does DEN see my dns?" (pick N probes near DEN) > "How does LHR see my dns?" (pick N probes near LHR) > "how does ...." > > ...you get the idea... I'm trying to characterize my service from a > 'user' perspective by large Metropolis, well within N km of that > metropolis anyway :) but across ~70 or so metros, in v4 and v6 and with > authoritative and non-authoritative queries with each test running for 4 > days so i can see some daily cycles in traffic patterns/etc. The number > of measurements is large in total, breaking up by 3-4 metropolis chunks > is super tedious :( > > Can I request an API key (or some other thing) which can make that sort > of request happen for all my measurements in one go? The thing I'm > probing is very able to handle a few extra thousand queries per second.. > and I'd only be hurting myself i get my estimate wrong :) I was part of a team on a hackathon a while back which needed to compute distances between points on the globe, including Atlas probes: https://github.com/shane-kerr/ripe-atlas-anycast-work I see that the openflights project has since moved to GitHub, and so you can get the IATA airport data here: https://github.com/jpatokal/openflights/blob/master/data/airports.dat I guess I should update the README.md... The repository is basically a last-point-in-time snapshot of the hackathon work, so it a bit rough. 😬 Anyway, this code is probably the closest to what you want: https://github.com/shane-kerr/ripe-atlas-anycast-work/blob/master/add-dist.py Turning the great_circle_dist() function into a filter across the set of all probes (meta-probes.json, which you can download in advance) should get you something like what you want. Note that this was all done 4 years ago according to GitHub, so maybe Atlas provides better tools for this nowadays. 😊 Cheers, -- Shane
- Previous message (by thread): [atlas] Making a bunch of tests/measurements to a single destination is 'tedious'
- Next message (by thread): [atlas] Making a bunch of tests/measurements to a single destination is 'tedious'
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]