Re: [atlas] Delays?

[Stephane Bortzmeyer]

On Mon, May 13, 2024 at 09:51:14PM +0200,
 Ernst J. Oud  wrote 
 a message of 22 lines which said:

> I experience delays on creating measurements.
> 
> Even after 2 minutes, a measurement is not running, eventually it will but it 
> used to take a couple of seconds.

Same here. With blaeu, I use the option --measurement-ID because,
after "some" time, the measurement is done so it is just a matter of
patience.

-- 
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net/mailman/listinfo/ripe-atlas

Re: [atlas] API advice to pull data from multiple measurements

[Christopher Amin]

Hi,

I have increased the maximum number of subscriptions per minute to
512, because it was a bit low at 120. You're right that the rate limit
values aren't documented, as they are tweaked now and then based on
usage patterns.

If you don't mind including measurement results from other running
measurements (not just DNSMON), you could alternatively experiment
with filtering by "destinationAddress". For example, this subscription
would capture *every* result to k-root over IPv4, all in one sub:

["atlas_subscribe",{"streamType":"result","destinationAddress":"193.0.14.129"}]

Hopefully one or both of these help you!

Regards,
Chris Amin
RIPE NCC

On Sat, 11 May 2024 at 09:11,  wrote:
>
> Hi,
>
> I would like to pull data from DNSMON probe measurements to build a real-time 
> view.
>
> Considering the combination of IPv4/IPv6, UDP/TCP, multiple nameservers per 
> TLD, it quickly adds up to 150+ measurements.
>
> I started with the streaming API, sending register messages for the 
> measurements of interest, but quite quickly I am getting errors with 
> "slow_down" response. I could not find the rate limit values in the 
> documentation of the streaming API.
>
> Using the HTTP API would also mean hundreds of API calls, one per measurement.
>
> What is the recommended way to regularly pull data from many measurements, to 
> avoid rate limiting or generating too much load on the API ?
>
> Regards
>
> --
> ripe-atlas mailing list
> ripe-atlas@ripe.net
> https://lists.ripe.net/mailman/listinfo/ripe-atlas

-- 
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net/mailman/listinfo/ripe-atlas

Re: [atlas] Delays?

[Johan ter Beest]

Hi Ernst,

We are aware and have put in place a mitigation that (fingers crossed)
seems to work. After the RIPE meeting, we are looking to make this a more
permanent solution.

Kind regards,
Johan

On Mon, 13 May 2024 at 21:51, Ernst J. Oud  wrote:

> I experience delays on creating measurements.
>
> Even after 2 minutes, a measurement is not running, eventually it will but
> it used to take a couple of seconds.
>
> My streaming api calls now time out…
>
> Is this known? Will it approve or do I need to change my scripts so that
> they wait longer?
>
> Regards,
>
> Ernst J. Oud
> --
> ripe-atlas mailing list
> ripe-atlas@ripe.net
> https://lists.ripe.net/mailman/listinfo/ripe-atlas
>
-- 
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net/mailman/listinfo/ripe-atlas