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/ripe-atlas@ripe.net/
[atlas] Querying your own measurements
- Previous message (by thread): [atlas] Querying your own measurements
- Next message (by thread): [atlas] No Ethernet activity on new probe
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sebastian Castro
sebastian at nzrs.net.nz
Wed Jan 27 20:01:16 CET 2016
On 27/01/16 9:37 PM, Robert Kisteleki wrote: > Hi, > >>> Can you provide your use case here? What's the purpose for getting a list of >>> your on measurements from a script? Shouldn't your scripts already know >>> about the measurements they started? :-) >>> >> >> That's usually the case, except when a there is a user interruption of >> the script, a strange failure case or any other that prevents the script >> to save the list of measurements at the right time :) > > That can indeed happen -- though one would hope it is really an exception. > > We have two other kinds of API keys requested earlier and in the pipeline, > so adding this third one is probably a minor increment in effort needed :-) > However, since we're about to make the v2 API official and eventually remove > v1, we'll most likely do this in the new version. Thanks, that's sensible. Will wait for v2 API then :) Cheers, > > Cheers, > Robert > > -- Sebastian Castro Technical Research Manager NZRS Ltd. desk: +64 4 495 2337 mobile: +64 21 400535
- Previous message (by thread): [atlas] Querying your own measurements
- Next message (by thread): [atlas] No Ethernet activity on new probe
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]