Jaap,

-----Original Message----- From: dnsmon-contact-bounces@ripe.net [mailto:dnsmon-contact- bounces@ripe.net] On Behalf Of Jaap Akkerhuis Sent: Wednesday, March 19, 2014 10:50 AM To: Vesna Manojlovic Cc: ncc-services-wg@ripe.net; dns-wg@ripe.net; RIPE Atlas People; dnsmon-contact@ripe.net; dnsmon-user@ripe.net; Measurement Analysis and Tools Working Group Subject: Re: [dnsmon-contact] [dnsmon-user] The Beta Version of the New DNSMON is Now Available

We invite you all to try the new service and provide your feedback. We're confident that the new DNSMON will continue to meet your needs and hope that you'll be happy with the new features.

It doesn't come anywhere close to the old service. E.g., the functionality of <http://dnsmon.ripe.net/dns-servmon/server/> is missing.

That's what I thought at first but actually it is there it just takes a little finding. Click on the TLD and you will get a list of servers down the left, if you then click on a server you will get something that looks very similar to the old server view. There are two things that I would really like to see: 1. The ability to pull some data out and pull it in to my own monitoring system for a familiar view for our operations engineers. 2. An ability to provide sms/e-mail alerting depending on certain (user definable) conditions. Brett Nominet UK.

Brett, On 2014.03.19. 12:02, Brett Carr wrote:

There are two things that I would really like to see:

1. The ability to pull some data out and pull it in to my own monitoring system for a familiar view for our operations engineers.

All the data for DNSMON are collected by RIPE Atlas as ongoing, public DNS measurements. The measurement IDs are exposed in the DNSMON interface ("Show RIPE Atlas measurements" button). There's a related discussion on the RIPE Atlas users' mailing list about an API to get to the *latest* results per measurement, which will come handy if you don't want to download gigs of results every time.

...

2. An ability to provide sms/e-mail alerting depending on certain (user definable) conditions.

To be slightly more specific,

https://labs.ripe.net/Members/suzanne_taylor_muzzin/introducing-ripe-atlas-s...

Something more DNS specific but similar to the above would be very useful.

This is entirely possible. In order to implement it, we'd like to keep the mechanism described in the article, but extend it to support DNS. Still, because determining success/failure of DNS measurements is a bit more tricky than pings, the details need some discussion. I invite all to have that discussion on the MAT-WG mailing list (also on cc now). Regards, Robert

Brett

On 20 Mar 2014, at 08:49, Robert Kisteleki <robert@ripe.net> wrote:

There's a related discussion on the RIPE Atlas users' mailing list about an API to get to the *latest* results per measurement, which will come handy if you don't want to download gigs of results every time.

It's a pity Robert that the discussion appears to be confined to that list. I expect many TLD and root operators would be interested in having some way of using DNSMON data to supplement their existing DNS monitoring arrangements. Not all of these will be paying customers for DNSMON or hosting Atlas probes. There may well be other fora too like CENTR or OARC who could have useful contributions to the development of this API. It would be nice if the DNS business could come up with a standard API/data format for this side of thing. OTOH, I can see why that could be considerably harder to achieve than cat-herding. Perhaps we can have the WG discuss this in Warsaw.

On 2014.03.20. 11:21, Jim Reid wrote:

On 20 Mar 2014, at 08:49, Robert Kisteleki <robert@ripe.net> wrote:

...

There's a related discussion on the RIPE Atlas users' mailing list about an API to get to the *latest* results per measurement, which will come handy if you don't want to download gigs of results every time.

It's a pity Robert that the discussion appears to be confined to that list. I expect many TLD and root operators would be interested in having some way of using DNSMON data to supplement their existing DNS monitoring arrangements. Not all of these will be paying customers for DNSMON or hosting Atlas probes. There may well be other fora too like CENTR or OARC who could have useful contributions to the development of this API.

It would be nice if the DNS business could come up with a standard API/data format for this side of thing. OTOH, I can see why that could be considerably harder to achieve than cat-herding.

Perhaps we can have the WG discuss this in Warsaw.

Jim, I don't really mind where the discussion happens, I'm more interested in making sure that it does happen, with that the interested parties are involved. And I was trying to avoid having multiple discussions on multiple mailing lists so named one: Atlas, because it will be an Atlas feature at the end of the process. Regards, Robert

Dear Jaap, On 2014.03.19. 11:49, Jaap Akkerhuis wrote:

We invite you all to try the new service and provide your feedback. We’re confident that the new DNSMON will continue to meet your needs and hope that you'll be happy with the new features.

It doesn't come anywhere close to the old service. E.g., the functionality of <http://dnsmon.ripe.net/dns-servmon/server/> is missing.

This server view exists in the new implementation too. One can reach it from the zone view, by clicking on the name on a particular server. We prepared for this use case since people are mostly interested in the servers of a (their) particular zone, not an alphabetical list. That said, we can make such a listing page if there's a need for it.

The UI page <https://atlas.ripe.net/dnsmon/doc/ui> is garbled.

That was an oops, but it is fixed already. Regards, Robert

All in all this is pretty bad.

jaap