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] No more a list of probes when the measurement is ongoing?
- Previous message (by thread): [atlas] No more a list of probes when the measurement is ongoing?
- Next message (by thread): [atlas] [UDM creation API] Which parameters are mandatory?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Stephane Bortzmeyer
bortzmeyer at nic.fr
Mon Jun 24 16:40:54 CEST 2013
On Mon, Jun 24, 2013 at 04:34:39PM +0200, Daniel Quinn <dquinn at ripe.net> wrote a message of 25 lines which said: > *However* if you're using `fields=` and are only making use of a few > fields *you are inadvertently hammering our servers for no good > reason*. I plead not guilty. This was an advice from Andreas Strikos and he uses this technique in his command-line tool <https://github.com/astrikos/ripe-atlas-cmdline> :-) > https://atlas.ripe.net/api/v1/measurement/1011817/?fields=probes It works, thanks. > More importantly, the `fields=` trick is a hack that may not stick > around for performance issues, so it's not a good idea to > standardise on it. The problem for the Atlas user is that there is little documentation on creating and management measurements so it is hard to know what is stable and what is not and what are the things you can rely on.
- Previous message (by thread): [atlas] No more a list of probes when the measurement is ongoing?
- Next message (by thread): [atlas] [UDM creation API] Which parameters are mandatory?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]