This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] built-in measurement id 12023
- Previous message (by thread): [atlas] built-in measurement id 12023
- Next message (by thread): [atlas] Retiring old ("legacy") UI pages and deprecated API calls
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Robert Kisteleki
robert at ripe.net
Tue Jan 23 09:15:37 CET 2024
Dear Xiao, You are absolutely right - the documentation (and the API metadata) incorrectly states 900 seconds, in reality it is once a day. Also for measurement 13023 over IPv6. (It would be possible to adjust reality to match the docs instead and adjust this measurement's frequency to 900 seconds, but considering the meaning of the measurement and that it has been running with said frequency all along, I'd prefer to fix the documentation.) Thank you for reporting this, we'll fix it shortly. Regards, Robert On 2024-01-23 02:06, Xiao Song wrote: > Hi all, > > Hope this email finds you well. > > The document says that this built-in measurement #12023 requires all > available probes to send http requests to the target every 900s, but > actually it seems like all probes send requests once a day. > I was wondering if there exists inconsistency between the document and > the actual measurements? > > Any suggestions would be appreciated. > > Thank you! > > Best, > Xiao >
- Previous message (by thread): [atlas] built-in measurement id 12023
- Next message (by thread): [atlas] Retiring old ("legacy") UI pages and deprecated API calls
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]