Hello.
I was implementing a mechanism to read the measurement results from the
Ripe Atlas for many asynchronous measurements. In this process, I have
faced multiple questions regarding the internal mechanisms of Ripe Atlas,
and I would be thankful if you could help me clarify them.
First, in the Ripe Atlas, I sometimes get “-1” in the result indicating
100% packet loss and sometimes very long RTTs. Can you tell me please what
is the condition when Ripe gives up on a target and marks it as "-1”?
Second, I have implemented asynchronous reading using web sockets and faced
a rate limit on several concurrent web socket connections. The error
message said:
'There are too many connections from this IP address. Try making multiple
subscriptions on the same connection.’
Can you tell me please, if there is a limit on the number of subscriptions
on the same connection?
To solve the issue in the second question, I implemented a polling
mechanism that periodically checks if the measurement is finished. In order
to not overload the API, I attempted to retrieve multiple measurement
results in a single call using the following API endpoint:
GET /api/v2/measurements/{pk}/latest/
The documentation of that API endpoint states: "Get the most recent results
from one or more measurements”. However, I need help understanding how to
specify multiple measurement IDs in this endpoint, because all options I
tried failed with HTTP status code 405 (Method Not Allowed). Could you
please show me the correct way of using this API endpoint?
Thank you!
With regards,
Huseyn Gambarov
-----
To unsubscribe from this mailing list or change your subscription options,
please visit: https://mailman.ripe.net/mailman3/lists/ripe-atlas.ripe.net/
As we have migrated to Mailman 3, you will need to create an account with the
email matching your subscription before you can change your settings.
More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
