UI: "Reuse from existing measurement" probe selection
Hello, when I'm using the "Reuse from existing measurement" probe selection method, only a single probe (the last probe looks like) from the existing measurement is used, not as expected all the probes from the existing measurement. The low expected daily cost is a good indicator for this as well, a part from actually starting a measurement and confirming that it only contains a single probe. I tried with a new and empty Google Chrome profile just to exclude any interaction with Firefox, browser caches, or the FF extensions I use, and the behavior is clearly reproducible. The UI also suggest that using a *subset* of the probes selected in a previous measurement is possible, however I have not found a way to actually select probes. The arrow pointing down is not doing anything for me (just endlessly loading nothing). This could absolutely be an embarrassing PBKAC issue, considering that I just spent an undisclosed amount of time the other day to diagnose why my anchor selection didn't work for the HTTP requests I was trying to run (of course it's not that you can only run HTTP requests from anchors, it's that you can only run HTTP requests *against* anchors as a target...). Thanks, Lukas
Hi Lukas, In my testing this works as expected. Would you mind providing the original and new measurement IDs, and I will take a look? As for the wording about subset, I think this could be clearer and I will look into changing the text a bit. But the reason it says set/subset is that over time the probes originally scheduled for a particular msm will degrade (some will be disconnected or abandoned), so you will usually not get all the probes that were scheduled originally, but rather a "subset" of them. Perhaps this could be the reason you did not get all the probes you expected in your new measurement? Kind regards, Stephen Atlas UI
On 16 Jul 2026, at 19:54, Lukas Tribus <lukas@ltri.eu> wrote:
Hello,
when I'm using the "Reuse from existing measurement" probe selection method, only a single probe (the last probe looks like) from the existing measurement is used, not as expected all the probes from the existing measurement. The low expected daily cost is a good indicator for this as well, a part from actually starting a measurement and confirming that it only contains a single probe.
I tried with a new and empty Google Chrome profile just to exclude any interaction with Firefox, browser caches, or the FF extensions I use, and the behavior is clearly reproducible.
The UI also suggest that using a *subset* of the probes selected in a previous measurement is possible, however I have not found a way to actually select probes. The arrow pointing down is not doing anything for me (just endlessly loading nothing).
This could absolutely be an embarrassing PBKAC issue, considering that I just spent an undisclosed amount of time the other day to diagnose why my anchor selection didn't work for the HTTP requests I was trying to run (of course it's not that you can only run HTTP requests from anchors, it's that you can only run HTTP requests *against* anchors as a target...).
Thanks,
Lukas ----- 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/
Hello Stephen, On Fri, 17 Jul 2026 at 10:06, Stephen Suess <ssuess@ripe.net> wrote:
Hi Lukas,
In my testing this works as expected. Would you mind providing the original and new measurement IDs, and I will take a look?
Thanks for getting back to me. I'm trying to mirror the measurement 189412791 with probes: 1011242,1002931,1006278,1004427,1000371,1009376,1000143,25035,22413,12120,22296,17758,54373 As you can see in the video below, measurement 191250776 contains only a single random probe of measurement 189412791, while if I specify them manually (measurement 191250888), it all works (maybe out of 13 I get 12 probes, that's fine). Video: https://dl.ltri.eu/2026-07-17-10-32-54-ripe-atlas-reuse.mp4
you will usually not get all the probes that were scheduled originally
Ok, got the meaning of the subset text now, perhaps a simplified wording would be "available probes" as opposed to "a set/subset of probes". While we are at it: Perhaps we can make the error about HTTP Request targeting non-anchors more friendly to the distracted brain that normalizes away everything after "only anchors", or is that just me? Replace: Only anchors may be targeted with: Both probes and anchors can execute HTTP measurements. However the HTTP target is limited to anchors. Best regards, Lukas
Hi Lukas, Thanks for the measurement IDs, they were very helpful. I have found the source of the issue, and am discussing with the team whether this should be fixed in the API or frontend. I will get back to you soon with a fix you can test and then we will roll this out to production. I will at the same time look into rewording the other messages to be a bit clearer. Thanks very much for the detailed information and feedback. Kind regards, Stephen Atlas UI On Fri, 17 Jul 2026 at 11:10, Lukas Tribus <lukas@ltri.eu> wrote:
Hello Stephen,
On Fri, 17 Jul 2026 at 10:06, Stephen Suess <ssuess@ripe.net> wrote:
Hi Lukas,
In my testing this works as expected. Would you mind providing the
original and new measurement IDs, and I will take a look?
Thanks for getting back to me.
I'm trying to mirror the measurement 189412791 with probes:
1011242,1002931,1006278,1004427,1000371,1009376,1000143,25035,22413,12120,22296,17758,54373
As you can see in the video below, measurement 191250776 contains only a single random probe of measurement 189412791, while if I specify them manually (measurement 191250888), it all works (maybe out of 13 I get 12 probes, that's fine).
Video: https://dl.ltri.eu/2026-07-17-10-32-54-ripe-atlas-reuse.mp4
you will usually not get all the probes that were scheduled originally
Ok, got the meaning of the subset text now, perhaps a simplified wording would be "available probes" as opposed to "a set/subset of probes".
While we are at it: Perhaps we can make the error about HTTP Request targeting non-anchors more friendly to the distracted brain that normalizes away everything after "only anchors", or is that just me?
Replace: Only anchors may be targeted
with: Both probes and anchors can execute HTTP measurements. However the HTTP target is limited to anchors.
Best regards,
Lukas
participants (2)
-
Lukas Tribus -
Stephen Suess