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/[email protected]/
[atlas] Selecting only anchors for UDM
- Previous message (by thread): [atlas] Selecting only anchors for UDM
- Next message (by thread): [atlas] Selecting only anchors for UDM
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Daniel Karrenberg
daniel.karrenberg at ripe.net
Wed Jun 11 12:25:05 CEST 2014
On 11.06.14 12:03 , Ondřej Caletka wrote: > Hello list, > > is there a way to run an UDM on Anchors only? I think it would be a good > feature, especially for precise latency measurement. > > Cheers, > Ondřej Caletka > Yes, that would be useful. I have been programming around this using the API to fetch the whole probe list first. I suggest an API extension to select probe types that is exposed in the UI : "probes": [ { "requested": 10, "type": "area", "probetype": "anchor", "value": "WW" } ] This is nicely general. One could later add probetypes like: "hasipv6" and "hardwarev3". If that is too much an extension a la "probes": [ { "requested": 10, "type": "anchor", "value": "WW" } ] would already help. Can we put that on the road-map? Anyone else who would like this in the UI and API? Daniel
- Previous message (by thread): [atlas] Selecting only anchors for UDM
- Next message (by thread): [atlas] Selecting only anchors for UDM
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]