Hi Seth, I just tested on our end, and I see the manage tab after using the API to create measurements. Can you send me some specific measurements you have made in both the api and the UI, and I will take a look? It would also help if you can send me the full spec you used to create your particular measurement (without your key of course). Kind regards, Stephen Atlas UI

On 1 Aug 2024, at 08:00, Seth David Schoen <schoen@loyalty.org> wrote:

Stephen Suess writes:

...

Hello Atlas Users,

We have released several updates to the UI over the past month. Here are some of the highlights:

- Measurement overview tab: improved summary info for various measurement types and (in the case of dns) most observed answers filtering - Measurement results tab: multiple, non-modal, resizable traceroute popups, toggles for filtering of no reply and no report items, and better error messaging when there are multiple sub queries

Hi Stephen,

I have a couple of recurring measurements that I wanted to stop (earlier than the originally entered stop time). The Atlas documentation says that there is a "Manage" tab with a stop button:

...

You can stop your active user-defined measurement by clicking the stop button on the "Manage" tab of the measurement details page.

I see this tab for my own recurring measurements that were created via the web interface, but not for those created via the API, even though it was under the same user ID. I didn't try this on the prior version of the web interface, so I don't know whether this is something that might have changed with the update.

Is there some sort of rule that a measurement that was created using the API can also only be modified via the API, even when logged in as the same Atlas user? I don't immediately see this mentioned in the documentation. ----- 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/

Hi again Seth, Ok, we have just figured out what is causing this. If a measurement has been hidden by a user, the manage tab would not show because the API did not return hidden results for the endpoint needed for the manage functions without an explicit API switch. The team is reviewing the best way to resolve this in the API, but in the meantime if you want to see the manage tab in the UI for these measurements, you only need go to your hidden list of measurements (https://atlas.ripe.net/measurements/mine?hidden=true&sort=-id&toggle=hidden&page_size=100&page=1) and unhide the ongoing measurements you wish to manage, then visit the details page for that measurement. Thanks very much for reporting this, we will have an API/UI fix for this soon. Kind regards, Stephen

On 6 Aug 2024, at 07:07, Seth David Schoen <schoen@loyalty.org> wrote:

Stephen Suess writes:

...

Hi Seth,

I just tested on our end, and I see the manage tab after using the API to create measurements. Can you send me some specific measurements you have made in both the api and the UI, and I will take a look? It would also help if you can send me the full spec you used to create your particular measurement (without your key of course).

Thanks, I sent you some examples off-list just now. It does seem to be a recurring discrepancy, but maybe the distinguishing factor isn't API vs. UI, as one example I found was created via the UI and also doesn't show me the Manage tab.