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] Atlas fully down..
- Previous message (by thread): [atlas] Atlas fully down..
- Next message (by thread): [atlas] Atlas fully down..
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Chris Amin
camin at ripe.net
Wed Sep 20 13:22:16 CEST 2023
On 20/09/2023 12:57, Ernst J. Oud wrote: > I checked my code that calls Magellan. It does not add the “system-ipv4-works“ tag to the request for probes in measurements. > > Does Magellan add that tag automatically? Hi Ernst, The system-ipv4-works (and system-ipv6-works) tags are specified in the configuration in the ripe-atlas-tools settings file. If you run: ripe-atlas configure --editor you can find a tags block with various default tag sets to use for different measurement types. *However*, as a workaround we have re-populated the system-ipv4-works and system-ipv6-works tags, so that the default behaviour of Magellan should be sane once again. This should allow scheduling of new measurements and streaming the results. Note: The probe sets for these tags are currently just copied from the system-ipv4-stable-1d and system-ipv6-stable-1d tags, respectively, which were not affected by this issue because they use a different data backend. The actual probe sets are therefore not exactly the same, but they are functionally very similar if your goal is "restrict the participating probes to ones that are likely to work".
- Previous message (by thread): [atlas] Atlas fully down..
- Next message (by thread): [atlas] Atlas fully down..
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]