Problems deleting measurements
Hi! I have problems with lots of measurements, I can not delete them. e.g: A) https://atlas.ripe.net/api/v1/measurement/1027747/ The status is "Failed" and in the web I can not Archive or Stop it. Also deletion via REST fails: curl -H 'Accept: application/json' -X DELETE https://atlas.ripe.net/api/v1/measurement/1027747/?key=01....6d {"error": {"code": 200, "message": "That measurement cannot be stopped."}} btw: is above REST call correct? Same problem for measurment 1012558 which is in status Stopped. B) Is "archive" in the web interface identical to "DELETE" via REST? E.g. the web interface offers me "Archive" for measurement 1029338 (and I am quite sure it would work), but the REST call fails with same result: curl -H 'Accept: application/json' -X DELETE https://atlas.ripe.net/api/v1/measurement/1029338/?key=01....d {"error": {"code": 200, "message": "That measurement cannot be stopped."}} Further, the web interface offers "Stop" and "Archive", but the REST call only offers "DELETE". So, how do I "Stop" via REST? For me it is confusing to have different terms in the web interface and REST API. C) 1031725: The measurement is currently (UTC 18:30) in status Ongoing. Start Time is UTC 19:45, Stop Time is 19:55. When I stop the measurement, the measurements stop time changes to the current time, but status is still Ongoing, and I can not Archive (not offered), but it still offers always Stop. But when I delete via REST, the measurement gets stopped (status Stopped in web interface). So does REST-DELETE is identical to "Stop" in web interface? If yes, how do I archive via REST? Further, DELETE a stopped message should not produce error "That measurement cannot be stopped.", but rather "That measurement is already stopped." D) For the web interface it would be cool to stop/archive/delete measurements more comfortable. Eg. select multiple measurements and then choose "stop and archive". Thanks Klaus Thanks Klaus
You've asked for a lot here, and for most of it, the best I can offer you is: "I understand (and even share) your concerns, but what you're asking for takes a lot longer to implement than you may like. However, we are working on clarifying the interface in this area." Now, regarding some of your confusion, I'll put it all in point-form to keep it simple: * There is no way to delete a measurement. Not via the website, and not via the REST API. * As REST offers 4 basic verbs for interface: GET, PUT, POST, and DELETE, we opted to use DELETE as the "STOP" method, as we have no intention of ever actually deleting measurements. * The concept of archiving measurements is being re-worked and may disappear only to be re-used later as a means of hiding the measurements from your list. We're still working on what the Right Way to handle this should be. I hope that clears things up for you.
Hi Daniel! Thanks for the info. IMO https://atlas.ripe.net/doc/rest -> last paragraph: "Deleting a Measurement" should be renamed and extended with the text below. And as I said, it would be nice to have an easy way to remove the measurements from the web interface (e.g. marking measurements with the "hide" flag, and in the web interface one can choose to see the normal view or also "show also hidden measurements"). This should be possible with REST too (setting/unsetting the "hide measurement" flag). Thanks Klaus On 03.10.2013 00:45, Daniel Quinn wrote:
You've asked for a lot here, and for most of it, the best I can offer you is: "I understand (and even share) your concerns, but what you're asking for takes a lot longer to implement than you may like. However, we are working on clarifying the interface in this area."
Now, regarding some of your confusion, I'll put it all in point-form to keep it simple:
* There is no way to delete a measurement. Not via the website, and not via the REST API. * As REST offers 4 basic verbs for interface: GET, PUT, POST, and DELETE, we opted to use DELETE as the "STOP" method, as we have no intention of ever actually deleting measurements. * The concept of archiving measurements is being re-worked and may disappear only to be re-used later as a means of hiding the measurements from your list. We're still working on what the Right Way to handle this should be.
I hope that clears things up for you.
participants (2)
-
Daniel Quinn -
Klaus Darilion