No more a list of probes when the measurement is ongoing?
I relied on a "probes" field in the <https://atlas.ripe.net/api/v1/measurement/1011817/?fields=> data to find out the number of probes allocated to a measurement. Now, it is no longer available :-( % curl 'https://atlas.ripe.net/api/v1/measurement/1011817/?fields=' {"can_visualise": false, "creation_time": 1372080547, "description": "IPv4 base connectivity tests with 46.226.105.0", "dst_addr": "46.226.105.0", "dst_asn": null, "dst_name": "46.226.105.0", "interval": null, "is_oneoff": true, "is_public": true, "msm_id": 1011817, "packets": 3, "probe_sources": [["Area", "WW", 10]], "resolve_on_probe": false, "resolved_ips": ["46.226.105.0"], "result": "/api/v1/measurement/1011817/result/", "start_time": 1372080547, "status": {"id": 2, "name": "Ongoing"}, "stop_time": null, "type": {"id": 1, "name": "ping"}} What is its replacement?
That's probably a bug I created when I tweaked the API to handle explicit field requests properly. I'll see what I can do to fix it today or tomorrow. *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*. The `fields` modifier is there so you can request *specific fields*, not simply grab everything. If you use it in this way, your request will work as you need: https://atlas.ripe.net/api/v1/measurement/1011817/?fields=probes That'll return to you a list of all the probes used in measurement #1011817. If you want the probes and the `msm_id`, then just do this: https://atlas.ripe.net/api/v1/measurement/1011817/?fields=probes,msm_id ...repeat until you have *exactly* what you need and no more. You limit your bandwith consumption and the load on our servers. 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. With that said though, as it was working this way before I broke it, I'll do what I can to fix it now :-)
On Mon, Jun 24, 2013 at 04:34:39PM +0200, Daniel Quinn <dquinn@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.
participants (2)
-
Daniel Quinn -
Stephane Bortzmeyer