New release in January, features you asked for...
Hi, we had a release 2 days ago, maybe you already noticed new features... * REST API -- althou in Beta! https://atlas.ripe.net/doc/rest * New costs for certain measurements: https://atlas.ripe.net/doc/credits & * 20 instead of 19 probes visualized in ping UDMs :) ... and if not, they are listed on RIPE Labs article: https://labs.ripe.net/Members/becha/ripe-atlas-january-2013-achievements ... and on the "announcements" page too: https://atlas.ripe.net/announce We are still working on "group access", and few more features are going to be announced to beta-testers soon. Share and enjoy! Regards, Vesna
On Fri, Feb 01, 2013 at 11:18:37AM +0100, Vesna Manojlovic <BECHA@ripe.net> wrote a message of 27 lines which said:
* REST API -- althou in Beta! https://atlas.ripe.net/doc/rest
If I read the documentation correctly, it is only to *read* data. If so, what's the point? There was already a way to access data (download the JSON file and parse it) and I regret that it will be deprecated ("is intended to replace the current ways of programmatically accessing RIPE Atlas data"). What is really missing is a way to *run* measurements, specially with variable parameters (such as the QNAME for DNS UDMs).
Stephane, On 2013.02.01. 12:44, Stephane Bortzmeyer wrote:
On Fri, Feb 01, 2013 at 11:18:37AM +0100, Vesna Manojlovic <BECHA@ripe.net> wrote a message of 27 lines which said:
* REST API -- althou in Beta! https://atlas.ripe.net/doc/rest
If I read the documentation correctly, it is only to *read* data. If so, what's the point? There was already a way to access data (download the JSON file and parse it) and I regret that it will be deprecated ("is intended to replace the current ways of programmatically accessing RIPE Atlas data").
The API is also meant to allow listing measurements ("search"). The same API will make it possible to specify measurements. So, so far there was a way to access data, now there's also a way to access metadata, and a consistent way forward for more interaction with the system.
What is really missing is a way to *run* measurements, specially with variable parameters (such as the QNAME for DNS UDMs).
This is coming. As the article states: "We'll start testing two new features soon: one-off measurements and the measurement specification API to start and stop user-defined measurements. Beta testers will help us adjust these features before we go live with them." Regards, Robert
On Fri, Feb 01, 2013 at 01:45:53PM +0100, Robert Kisteleki <robert@ripe.net> wrote a message of 31 lines which said:
As the article states: "We'll start testing two new features soon: one-off measurements and the measurement specification API to start and stop user-defined measurements.
Just to be sure: this API will also allow to define new UDMs, not just start/stop existing ones? (I would like to run several slightly different UDMs sequentially)
On Feb 1, 2013, at 2:17 PM, Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote:
On Fri, Feb 01, 2013 at 01:45:53PM +0100, Robert Kisteleki <robert@ripe.net> wrote a message of 31 lines which said:
As the article states: "We'll start testing two new features soon: one-off measurements and the measurement specification API to start and stop user-defined measurements.
Just to be sure: this API will also allow to define new UDMs, not just start/stop existing ones? (I would like to run several slightly different UDMs sequentially) Yes you will be able to create new ones as well.
Regards, Andreas
participants (4)
-
Andreas Strikos -
Robert Kisteleki -
Stephane Bortzmeyer -
Vesna Manojlovic