[Dnsmon-test] Native Resolution etc
Robert Kisteleki
robert at ripe.net
Tue Mar 11 13:51:13 CET 2014
On 2014.03.11. 12:47, Daniel Karrenberg wrote:
>
> Thank you for making native resolution available. It is very very useful in isolating events in time and in getting a feel for what is happening during short intervals when significant changes happen. For the same reason I would like to see shorter aggregation buckets in other views too when the selected time interval is short, e.g. I want to be able to pinpoint the exact time when multiple servers serving a particular domain degrade. This would enhance the (perception of) usefulness of dnsmon in incident reporting.
We'll look into this.
> For the same reason I would like to see a combination view of all measurements using the same transport, e.g. IPv4/UDP.
>
> What puzzles me are differences between dnsmon classic and new like this example:
>
>
> http://dnsmon.ripe.net/dns-servmon/server/plot?server=b.root-servers.net;type=drops;tstart=1392105600;tstop=1392127199;af=ipv4
>
> https://atlas.ripe.net/dnsmon/index-page?dnsmon.server=192.228.79.201&dnsmon.zone=root&dnsmon.type=probes&dnsmon.startTime=1394515417&dnsmon.endTime=1394536533&dnsmon.selectedRows=&dnsmon.isTcp=true&dnsmon.session.show-filter=pls&dnsmon.session.color_range_pls=0-66-66-99-100&dnsmon.session.exclude-errors=true
>
> I have the impression that we are loosing significant signal here. Or is this just an illustration why silent retries were not a good idea?
>
> Daniel
Silent retries did indeed hide a lot of operational issues. We introduced
the no-retry policy (after the discussion on this list) on 5 March, as
illustrated by this viz:
https://atlas.ripe.net/dnsmon/group/fr.?dnsmon.server=2001:500:2e::2&dnsmon.zone=fr.&dnsmon.type=probes&dnsmon.startTime=1393977600&dnsmon.endTime=1394064000&dnsmon.selectedRows=&dnsmon.session.show-filter=pls&dnsmon.session.color_range_pls=0-7-7-71-100&dnsmon.session.exclude-errors=true
Your above timeframe is before the no-retry change.
Regards,
Robert