[dns-wg] [ncc-services-wg] [dnsmon-user] The Beta Version of the New DNSMON is Now Available

On 2014.09.08. 15:17, Bill Woodcock wrote:
> 
> Anything that can be done about the bad AS48294 probe, that doesn’t actually
> have IPv6 connectivity?  Can you have it stop reporting its lack of IPv6
> connectivity, or exclude it from results, or something?  It makes it hard to
> see what’s going on in overview results, if it’s constantly adding to the
> floor of measurements it contributes to.  Obviously, I’d prefer a
> generalized solution that applied to all such non-functional probes.
> 
> Thanks.
> 
> 
>                                 -Bill

Hello,

(keeping only the DNS-WG in the address list)

Even though we ask for stable IPv4+IPv6 connectivity from all Anchor hosts,
reality is that some are more flaky than others. At the moment we don't have
a clear policy on whether to remove these from DNSMON measurements, and if
so, when. (Is an hour of non-working a good trigger? A day, a week, a month,
a year? Should it be put back if it behaves again? Should the historic
results be changed for the affected period by this removal?)

In virtually all such cases we're in contact with the host to resolve the
issue. As you can imagine, sometimes it takes time.

What you can do now is exclude particular anchor from the visualisation
(press shift in the server view). This only affects that view in the UI, and
does not exclude that probe from the aggregate results.

Regards,
Robert