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] [UDM] What value to give to 'requested' when 'type' = 'msm'?
- Previous message (by thread): [atlas] [UDM] What value to give to 'requested' when 'type' = 'msm'?
- Next message (by thread): [atlas] [UDM] What value to give to 'requested' when 'type' = 'msm'?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Andreas Strikos
astrikos at ripe.net
Wed Jul 17 09:06:26 CEST 2013
Hi, On 7/16/13 4:21 PM, Stephane Bortzmeyer wrote: > The documentation > <https://atlas.ripe.net/doc/measurement-creation-api/> says: > > "probes": [ > { > "requested": 1, > "type": "msm", > "value": 1000002 > } > ] > > but, from my tests, if you do so, you get only one probe, whatever > measurement #1000002 actually used. To get all the probes, I had to > indicate a very large number in 'requested' (unless you remember or > count the actual number). > > Indeed if you want all probes you have to specify number bigger or equal with what the measurement had. Otherwise you will get the amount you specified. But it makes sense to have a flag to indicate that you want the exact same number. We will look into it. Thanks, Andreas
- Previous message (by thread): [atlas] [UDM] What value to give to 'requested' when 'type' = 'msm'?
- Next message (by thread): [atlas] [UDM] What value to give to 'requested' when 'type' = 'msm'?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]