Hi, For your first question, there is unfortunately still not a good way to find out why certain probes did not end up participating in measurements. One common reason is that a probe is thought to be online at the moment of scheduling, but subsequently disconnects and is unable either to receive the measurement request, or unable to deliver the result (in time).
As for a reasonable timeout: it can vary based on probes connection status and the business of the overall RIPE Atlas system. If I run a oneoff measurement with 100 probes right now (when the system is not very busy) I see the first result within 10 seconds, and 98 results within 20 seconds, with 2 probes never reporting. You could perhaps come up with a policy that you'll wait for the first result, and then wait a certain amount longer before giving up on remaining probes. I would advise you to experiment with thresholds to see what works for you, just keep in mind that the delay for the first result in particular can vary based on how busy the system is. I appreciate I didn't fully answer your questions, but I hope this helps a bit. Let me know if you have any followup questions. Cheers, Chris On Thu, 12 Dec 2024 at 18:55, Huseyn Gambarov via ripe-atlas < [email protected]> wrote: > Hello. > > > I am currently working on a project that heavily relies on Ripe Atlas Ping > measurements. During the development, I noticed that sometimes when, > let’s say, I request 3 probes, only 2 are participating in the > measurement. > > In the Ripe Archive, I found that there was a similar discussion here - > https://mailman.ripe.net/archives/list/[email protected]/thread/D6QZS4WC55NK2UBPWKPSMUMV5RMG6BE2/#TBX3FXJWQSOTVBUQXERGOZXHRACRIIGZ > > > > I have two questions, that I could not find answers to, and I would be > very grateful if you could help me with them. > > > First, in the mentioned discussion it is said that there are multiple > reasons why fewer probes are participating and there is ongoing work to > allow users to obtain information about specific conditions that occurred > during the measurement creation. Can you tell, if there is a way to get > that information via API? > > > Second, do you know if there is a reasonable timeout to wait before a new > attempt to reschedule the probe that failed to participate in the first > measurement? > > > Thank you for your help. > > 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/
----- 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/
