[atlas] Measurements at an interval

Hi Daniel,

I sent an email (included below.) outlining a measurement with a 
specific interval done through the API and listed the response, please 
look at the email below. As for the Web UI measurement here is an example:

    /{u'result': u'/api/v1/measurement/1044471/result/', u'status':
    {u'id': 4, u'name': u'Stopped'}, u'msm_id': 1044471, u'interval':
    1200, u'description': u'', u'participant_count': 50,
    u'can_visualise': False, u'resolve_on_probe': False, u'start_time':
    1386161734, u'af': 6, u'creation_time': 1386161734, u'is_oneoff':
    False, u'stop_time': 1386165633,
    u'all_scheduling_requests_fulfilled': True, u'resolved_ips':
    [u'2001:7b8:40:1:d0e1:0:0:1'], u'dst_asn': u'12859', u'query':
    {u'type': u'AAAA', u'class': u'IN', u'value': u'nlnetlabs.nl.'},
    u'is_public': True, u'type': {u'id': 7, u'name': u'dns'},
    u'dst_addr': u'2001:7b8:40:1:d0e1:0:0:1', u'dst_name':
    u'2001:7b8:40:1:d0e1::1'}//
    /


Robert Kisteleki suggested I send it through to atlas at ripe.net which I 
did and it has been listed as:

[ripe.net #1113749]

I received a response from Robert Kisteleki (which is the very last 
email included below), he said it might be a week or later until this 
gets investigated so he was right on the money :-) .

Thank you for your response and we hope to see this bug(or whatever it 
is) get squashed :D

P.S. If you could, please include Willem Toorop(Willem at nlnetlabs.nl) in 
the response as he was the one to mention this limitation to me and the 
one who suggested I email about this. He also sent an email outlining 
this issue but heard no response so I'm sure he would like to hear when 
a resolution to this limitation/bug/whatever has been found.

P.P.S. At the bottom of the first included email is our work around 
which is get the probes specific to our needs (ipv6/4 etc..) and the 
chunk them into sizable chunks(50 probes work).

Kind regards,
Warwick Louw

-------- Original Message --------
Subject: 	Re: [atlas] Measurements at an interval
Date: 	Wed, 04 Dec 2013 14:04:05 +0100
From: 	warwick <warwick at nlnetlabs.nl>
To: 	atlas at ripe.net



Hello,

Regarding the previous email: Measurements at an interval, below is the 
Json constructed for the measurement:
/
/

    /{'definitions': [{'description': '', 'use_probe_resolver': False,
    'af': 6, 'query_argument': 'nlnetlabs.nl', 'query_type': 'AAAA',
    'interval': 1200, 'query_class': 'IN', 'type': 'dns', 'is_oneoff':
    False, 'recursion_desired': False, 'target':
    '2001:7b8:40:1:d0e1::1'}], 'stop_time': 1386168052, 'probes':
    [{'requested': 100, 'type': 'area', 'value': 'WW'}]}/


And below is the response:

    /{"error": {"code": 104, "message": "You do not have enough credit
    to schedule this measurement."}}/


It seems as though it's a trivial mistake, that I might actually not 
have enough credits to perform this measurement but I'm sure I do since 
it's a simple DNS query with only 100 probes.

With 50 probes:

    /{'definitions': [{'description': '', 'use_probe_resolver': False,
    'af': 6, 'query_argument': 'nlnetlabs.nl', 'query_type': 'AAAA',
    'interval': 1200, 'query_class': 'IN', 'type': 'dns', 'is_oneoff':
    False, 'recursion_desired': False, 'target':
    '2001:7b8:40:1:d0e1::1'}], 'stop_time': 1386168333, 'probes':
    [{'requested': 50, 'type': 'area', 'value': 'WW'}]}/


This request is executed as expected. With the following response:

    /{u'measurements': [...]}/ (measurement id removed.)


To get past this problem we have been chunking our probes in groups of 
50. I just thought you might be interested.

Kind regards,
Warwick Louw




-------- Original Message --------
Subject: 	[ripe.net #1113749] Re: [atlas] Measurements at an interval
Date: 	Wed, 4 Dec 2013 15:24:32 +0100
From: 	Robert Kisteleki <atlas at ripe.net>
Reply-To: 	atlas at ripe.net
To: 	warwick at nlnetlabs.nl



Hi,

Got it, we'll look into this (probably early next week when the best person for this is back).

Regards,
Robert


On 2013-12-04 14:09:08, warwick at nlnetlabs.nl wrote:
> Hello,
>
> Regarding the previous email: Measurements at an interval, below is the
> Json constructed for the measurement:
> /
> /
>
>     /{'definitions': [{'description': '', 'use_probe_resolver': False,
>     'af': 6, 'query_argument': 'nlnetlabs.nl', 'query_type': 'AAAA',
>     'interval': 1200, 'query_class': 'IN', 'type': 'dns', 'is_oneoff':
>     False, 'recursion_desired': False, 'target':
>     '2001:7b8:40:1:d0e1::1'}], 'stop_time': 1386168052, 'probes':
>     [{'requested': 100, 'type': 'area', 'value': 'WW'}]}/
>
>
> And below is the response:
>
>     /{"error": {"code": 104, "message": "You do not have enough credit
>     to schedule this measurement."}}/
>
>
> It seems as though it's a trivial mistake, that I might actually not
> have enough credits to perform this measurement but I'm sure I do since
> it's a simple DNS query with only 100 probes.
>
> With 50 probes:
>
>     /{'definitions': [{'description': '', 'use_probe_resolver': False,
>     'af': 6, 'query_argument': 'nlnetlabs.nl', 'query_type': 'AAAA',
>     'interval': 1200, 'query_class': 'IN', 'type': 'dns', 'is_oneoff':
>     False, 'recursion_desired': False, 'target':
>     '2001:7b8:40:1:d0e1::1'}], 'stop_time': 1386168333, 'probes':
>     [{'requested': 50, 'type': 'area', 'value': 'WW'}]}/
>
>
> This request is executed as expected. With the following response:
>
>     /{u'measurements': [...]}/ (measurement id removed.)
>
>
> To get past this problem we have been chunking our probes in groups of
> 50. I just thought you might be interested.
>
> Kind regards,
> Warwick Louw
>


-- 

Robert Kisteleki, R&D Manager, RIPE NCC
RIPE Atlas Team




-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ripe/mail/archives/ripe-atlas/attachments/20131213/8aecf529/attachment.html>