<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">Malte,<div><br></div><div>Yes, I noticed the same thing. I have a long running measurement for which I regularly check to include new or exclude disconnected probes.</div><div><br></div><div>As a result it now shows 177 requested and 29 participating, but it currently shows 34 measurement results (<a href="https://atlas.ripe.net/measurements/45518789/#general">https://atlas.ripe.net/measurements/45518789/#general</a>).</div><div><br></div><div>It does not at all add up.</div><div><br></div><div><div dir="ltr">Regards,<br><div><br></div><div>Ernst J. Oud</div></div><div dir="ltr"><br><br id="lineBreakAtBeginningOfSignature"><div dir="ltr">Met vriendelijke groet,<div><br></div><div>Ernst J. Oud</div></div><blockquote type="cite">On 8 Apr 2024, at 08:30, Malte Tashiro via ripe-atlas <ripe-atlas@ripe.net> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><span>Hi,</span><br><span></span><br><span>I'm currently looking at measurement metadata and am a bit confused about the different ways of getting the number of probes participating in a measurement and the number of probes requested by the user.</span><br><span></span><br><span>I'd like to know how to...</span><br><span> 1. get the number of probes _currently_ participating in a measurement (for ongoing measurements)</span><br><span> 2. the number of probes that participated when the measurement finished (for stopped measurements)</span><br><span> 3. the number of probes a user requested over the lifetime of a measurement</span><br><span></span><br><span>The default response to /measurements returns a participant_count and a probes_requested value. However, there are also the optional fields current_probes and participation_requests and these do not add up.</span><br><span></span><br><span>For example, this [0][1] measurement (not mine) has a participant_count of 0 (showing as "Actually Participating: None") in the web interface, but one probe listed in current_probes, which shows up in the "Latest Results" list and is still performing measurements (at least while writing this).</span><br><span>So it seems like the current_probes list is more accurate to get the number of probes _currently_ (or when the measurement finished) participating in a measurement?</span><br><span></span><br><span>Similarly, there are 35 probes_requested, which equals the sum of "requested" probes from the participation_requests, however, some request are actually "remove" actions, which should not be included in this count?</span><br><span></span><br><span>Any hints on how to interpret these fields?</span><br><span></span><br><span>I think the requested probes and participation requests are more a problem for long-running measurements, but the participant count is sometimes weird for one-offs as well.</span><br><span></span><br><span>Thanks,</span><br><span>Malte</span><br><span></span><br><span>[0] https://atlas.ripe.net/measurements/67903255</span><br><span>[1] https://atlas.ripe.net/api/v2/measurements/67903255?optional_fields=current_probes,participation_requests<div><OpenPGP_0x7D82498BEF2E08F8.asc></div><span>-- </span><br><span>ripe-atlas mailing list</span><br><span>ripe-atlas@ripe.net</span><br><span>https://mailman.ripe.net/</span><br></span></div></blockquote></div></body></html>