Re: [atlas] Behind the scenes changes to measurement creation
Dear Alex, Apologies, thank you for picking up on this. The stop_time and start_time lt, lte, gt and gte fields were incorrectly working like their exact match counterpart. This has now been fixed and these filters should work as expected. Kind regards, Chris On 18/04/2017 14:04, Alexandros Milolidakis wrote: > Hi Chris , > It seems that stop_time , start_time etc don't work anymore. > For example picking all trace route measurements which stopped before > yesterday yields no results. > https://atlas.ripe.net:443/api/v2/measurements/?stop_time__lt=1492469625&type=traceroute > Could you take look? > Thanks > Alex > > Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum > > signature.asc Description: OpenPGP digital signature
Re: [atlas] Behind the scenes changes to measurement creation
Hi Chris , It seems that stop_time , start_time etc don't work anymore. For example picking all trace route measurements which stopped before yesterday yields no results. https://atlas.ripe.net:443/api/v2/measurements/?stop_time__lt=1492469625&type=traceroute Could you take look? Thanks Alex Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum
Re: [atlas] Behind the scenes changes to measurement creation
Dear all, There were several problems with these changes that have now been fixed: * When creating groups of measurements at the same time, only the first one would have probes scheduled, meaning that the other measurements would not receive results. This happened for 26 measurement creation requests before being fixed. * Measurements were scheduled more slowly so you may have seen delays before getting results. * Some measurements created using the API would display an error when viewing their details on the UI; these measurements have been fixed, and the problem no longer exists for new measurements. * The API became temporarily more strict in accepting certain values, which caused the command-line tools to stop working for some measurement types. The API has reverted to being more liberal in these cases, although this may be deprecated in the future -- any changes will be communicated clearly. Apologies for any inconvenience that these issues may have caused. Please do let us know if you notice anything else unusual when scheduling and using RIPE Atlas measurements. Kind regards, Chris Amin RIPE NCC On 06/04/2017 13:59, Chris Amin wrote: > Today we deployed behind-the-scenes changes to the measurement creation > process, both when using the website and the REST API. These changes > should not have any visible effects, with the exception of improvements > to the measurement API reference[1] to make it easier to see which > options belong to which measurement type. > > Although we've tested these changes extensively, they are significant so > I am sending this mail to ask you to please let us know if you notice > any problems or changes when creating measurements. > > Kind regards, > Chris Amin > RIPE NCC > > [1] https://atlas.ripe.net/docs/api/v2/reference/#!/api/Measurement_List_GET > signature.asc Description: OpenPGP digital signature
[atlas] Behind the scenes changes to measurement creation
Dear colleagues, Today we deployed behind-the-scenes changes to the measurement creation process, both when using the website and the REST API. These changes should not have any visible effects, with the exception of improvements to the measurement API reference[1] to make it easier to see which options belong to which measurement type. Although we've tested these changes extensively, they are significant so I am sending this mail to ask you to please let us know if you notice any problems or changes when creating measurements. Kind regards, Chris Amin RIPE NCC [1] https://atlas.ripe.net/docs/api/v2/reference/#!/api/Measurement_List_GET signature.asc Description: OpenPGP digital signature
