[atlas] Cannot understand the daily limit
- Previous message (by thread): [atlas] Cannot understand the daily limit
- Next message (by thread): [atlas] Starting again a stopped custom measurement
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jasper den Hertog
jdenhertog at ripe.net
Wed Mar 22 09:29:33 CET 2017
Stephane, You’re right. The official documentation suggests to put the ‘is_oneoff’ flag inside the ‘definitions’ object of the request. We’ll adapt the documentation to say we prefer the flag to be in the root object and we will promote a nested is_oneoff to the root object if it’s not clashing with other measurements in the request object. greetings, Jasper > On 21 Mar 2017, at 17:14, Stephane Bortzmeyer <bortzmeyer at nic.fr> wrote: > > On Tue, Mar 21, 2017 at 03:11:46PM +0100, > Stephane Bortzmeyer <bortzmeyer at nic.fr> wrote > a message of 15 lines which said: > >> But I'm still puzzled about exactly what happened. I checked my >> previous measurements (such as #7932387) and they were clearly >> marked "This is a one-off measurement" (otherwise, I would have >> burned all my credits for a long time!) > > And the official documentation disagrees with > you. <https://atlas.ripe.net/docs/api/v2/reference/#!/measurements/Measurement_List_POST> > lists is_oneoff both at the top-level of the JSON object, and under > "definitions". > -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2619 bytes Desc: not available URL: <https://lists.ripe.net/ripe/mail/archives/ripe-atlas/attachments/20170322/d7c8c224/attachment.p7s>
- Previous message (by thread): [atlas] Cannot understand the daily limit
- Next message (by thread): [atlas] Starting again a stopped custom measurement
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]