Cannot understand the daily limit
RIPE Atlas just denied me a measurement: "{"error":{"status":400,"code":104,"detail":"Executing this measurement request would violate your maximum daily spending limit of 1000000 credits. Please stop some of your currently running measurements and try again.","title":""}}" I have one permanent measurement, which takes, according to <https://atlas.ripe.net/user/credits/>, 3400 credits/hour (81600/day). Otherwise, I ran only one-off measurements, most taking < 1000 credits. How could I hit a limit of ONE MILLION per day?
Hi Stephane, It would be very helpful if you would share your measurement definition. WBR /vty On 3/20/17 5:07 PM, Stephane Bortzmeyer wrote:
RIPE Atlas just denied me a measurement:
"{"error":{"status":400,"code":104,"detail":"Executing this measurement request would violate your maximum daily spending limit of 1000000 credits. Please stop some of your currently running measurements and try again.","title":""}}"
I have one permanent measurement, which takes, according to <https://atlas.ripe.net/user/credits/>, 3400 credits/hour (81600/day). Otherwise, I ran only one-off measurements, most taking < 1000 credits.
How could I hit a limit of ONE MILLION per day?
On Tue, Mar 21, 2017 at 09:25:36AM +0100, Viktor Naumov <vnaumov@ripe.net> wrote a message of 20 lines which said:
It would be very helpful if you would share your measurement definition.
For instance: {'definitions': [{'query_class': 'IN', 'description': 'DNS resolution of www.afnic.fr', 'af': 4, 'query_argument': 'www.afnic.fr', 'query_type': 'AAAA', 'type': 'dns', 'is_oneoff': True, 'recursion_desired': True, 'use_probe_resolver': True}], 'probes': [{'requested': 300, 'type': 'area', 'value': 'WW', 'tags': {'include': ['system-resolves-a-correctly', 'system-resolves-aaaa-correctly']}}]} => Status 400, reason "{"error":{"status":400,"code":104,"detail":"Executing this measurement request would violate your maximum daily spending limit of 1000000 credits. Please stop some of your currently running measurements and try again.","title":""}}" My RIPE account is bortzmeyer+ripe@nic.fr
The system thinks that you are creating a recurrent measurements which costs above 1M. You're putting the one-off flag inside definitions but it must be outside. Like {"is_oneoff": true, "definitions": [.... /vty On 3/21/17 9:50 AM, Stephane Bortzmeyer wrote:
On Tue, Mar 21, 2017 at 09:25:36AM +0100, Viktor Naumov <vnaumov@ripe.net> wrote a message of 20 lines which said:
It would be very helpful if you would share your measurement definition. For instance: {'definitions': [{'query_class': 'IN', 'description': 'DNS resolution of www.afnic.fr', 'af': 4, 'query_argument': 'www.afnic.fr', 'query_type': 'AAAA', 'type': 'dns', 'is_oneoff': True, 'recursion_desired': True, 'use_probe_resolver': True}], 'probes': [{'requested': 300, 'type': 'area', 'value': 'WW', 'tags': {'include': ['system-resolves-a-correctly', 'system-resolves-aaaa-correctly']}}]}
=> Status 400, reason "{"error":{"status":400,"code":104,"detail":"Executing this measurement request would violate your maximum daily spending limit of 1000000 credits. Please stop some of your currently running measurements and try again.","title":""}}"
My RIPE account is bortzmeyer+ripe@nic.fr
On Tue, Mar 21, 2017 at 12:30:05PM +0100, Viktor Naumov <vnaumov@ripe.net> wrote a message of 20 lines which said:
The system thinks that you are creating a recurrent measurements which costs above 1M. You're putting the one-off flag inside definitions but it must be outside. Like {"is_oneoff": true, "definitions": [....
It worked before, I guess it changed with API v2. OK, I modify.
On Tue, Mar 21, 2017 at 12:30:05PM +0100, Viktor Naumov <vnaumov@ripe.net> wrote a message of 20 lines which said:
The system thinks that you are creating a recurrent measurements which costs above 1M. You're putting the one-off flag inside definitions but it must be outside. Like {"is_oneoff": true, "definitions": [....
OK, it works, thanks, I can now ask measurements with a lot of probes. 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!)
On Tue, Mar 21, 2017 at 03:11:46PM +0100, Stephane Bortzmeyer <bortzmeyer@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".
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@nic.fr> wrote:
On Tue, Mar 21, 2017 at 03:11:46PM +0100, Stephane Bortzmeyer <bortzmeyer@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".
participants (3)
-
Jasper den Hertog -
Stephane Bortzmeyer -
Viktor Naumov