Hi, I understand your point and recognise this is inconvenient at the moment. I'd say in the short term we can increase the limit - 25 is just a number like any other :-) - and perhaps administratively close the failing measurements. While I can't make promises about when, but in the longer term we can address this by looking at the the total results towards a target per time interval, instead of total measurements. Cheers, Robert On Thu, Jul 11, 2024 at 11:19 AM Malte Tashiro via ripe-atlas <ripe-atlas@ripe.net> wrote:
Hi Robert,
thanks for the clarification, now I know it is not a bug.
With that said, I think this necessitates some form of house-keeping task seeing how long Atlas has been active.
I looked at the 25 running measurements (attached), assuming [0] is the right request:
- 23 ping measurements, 1 traceroute, 1 SSL - 7 are dead (-> /latest endpoint returns no results) - Average participant count of 5 probes - None have a scheduled stop time - The last one was started on 2023-01-11, so it was not possible to schedule measurements targeting google.com since then?
I know the Atlas developers always have a lot on their plate, so I won't ask for anything, but maybe it would make sense to have a process that notifies users of long-running / infinite measurements that did not return results since x amount of time due to probes getting disconnected if they want to add new probes or cancel the measurement. And if they don't reply for y time, force cancel the measurement (or exclude them from the limit).
Anyways, at least now it is clear to me what is happening, so thank you.
Best, Malte
[0] https://atlas.ripe.net/api/v2/measurements/?status=2&target=google.com -- ripe-atlas mailing list -- ripe-atlas@ripe.net To unsubscribe send an email to ripe-atlas-leave@ripe.net