- ripe-atlas - mailman.ripe.net

Warnings about running out of credits and runaway measurements
by Robert Kisteleki 18 Feb '13

18 Feb '13

Dear Atlas users, Today we're going to enable two features that have been forecasted in the January 2013 Atlas update (https://labs.ripe.net/Members/becha/ripe-atlas-january-2013-achievements) Both of these features are intended to prevent runaway measurements which consume system resources, and to limit the resources used by users who don't contribute (any more) to the system; thus they both contribute to the stability and scalability of RIPE Atlas. They are both controlled by the credit system. The first feature is about sending warning emails if someone is about to run out of credits. That is, if the current credit consumption rate (with a two day lookback period) seems to use up all credits of a particular user within the next week or so, then we'll send an email about this. This allows the user to organise some extra credits, or stop some less important measurements in due time. The second feature stops measurements if someone actually runs out of credits. For now we'll use a *warning only* mode -- that is, the process will not actually stop measurements, it will only send emails. After a couple of weeks we'll change this to actually stop (some of the) measurements as well as notify the user. Our tests show that at the moment there are about a dozen people who would see effects of these processes. Both of these are necessary steps towards removing the existing limits imposed by the system (such as maximum amount of probes that can be used). Please let us know if you have questions or concerns, either on this mailing list, or (privately) by sending a mail to atlas(a)ripe.net Best regards, Robert Kisteleki RIPE Atlas team

1 0

Phase 1 of RIPE Atlas Anchors pilot - report on RIPE Labs
by Vesna Manojlovic 15 Feb '13

15 Feb '13

Dear community, [apologies for the duplicates] we just published an article on RIPE Labs with the status & features available for the hosts of RIPE Atlas Anchor boxes after the Phase 1: https://labs.ripe.net/Members/becha/ripe-atlas-anchors-pilot-update-on-phas… Share and enjoy :) Vesna

1 0

UDM destinations also visible in RIPEstat
by Vesna Manojlovic 13 Feb '13

13 Feb '13

Hi, I just wanted to share one more RIPE Atlas-related feature of RIPEstat: when querying for a IP prefix or AS number, you can now see all the UDMs that terminate in the IP addresses in that ASN or prefix, in the "Activity" tab, called "RIPE Atlas measurements targets". (picture attached) Below is a reminder of the feature to see all the probes, too. Happy measuring! Vesna -------- Original Message -------- Subject: [atlas] Atlas probes visible in RIPEstat Date: Fri, 21 Dec 2012 10:11:26 +0100 From: Vesna Manojlovic <BECHA(a)ripe.net> To: RIPE Atlas People <ripe-atlas(a)ripe.net> Dear RIPE Atlas users, this might be of interest to you too -- it is now possible to see coverage of Atlas probes in any ASN, prefix or *country* in RIPEstat! It works both as a widget and as CLI: https://stat.ripe.net/widget/atlas-probes#w.resource=212/12 or whois -h stat.ripe.net AS3333 If you decide to embed this widget somewhere on your page, please do let us know, we like to see our work being used :) More interesting RIPEstat features in the article on RIPELabs: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripestat-2012-december-… Cheers, Vesna

1 0

RIPE Atlas Community repository on GitHub
by Vesna Manojlovic 08 Feb '13

08 Feb '13

Hi everyone, an appropriate pastime for Friday afternoon - playing with GitHub ;-) I initially created https://github.com/RIPE-Atlas-Community/ripe-atlas-community-contrib for the contributions by you (and atlas-dev team) of the small programs, scripts, etc -- for visualizing RIPE Atlas measurements, analysing measurements data, and so on. We already had them listed here: https://atlas.ripe.net/doc/code However, GitHub seems to be *the* place for the community to exchange the code, so I am hoping that this repository will help share and maintain, and produce more code, and make it more useful for the rest of the world. First code in there is the one I inserted, created by Philip Homburg: "probes2kml.py", that shows probes on Google Earth. Please "add" more, or "link" your own contributions to this repository... ... or let me know how I can help to collect more of the RIPE Atlas specific code to this repository: from Wolfgang, Inigo, and others. Share and enjoy :) Regards, Vesna

1 0

Partial downtime over the weekend
by Robert Kisteleki 04 Feb '13

04 Feb '13

Dear all, On Friday we added the first devices of the upcoming next generation Atlas probes to our production network. Unfortunately, this triggered a bug in our controlling infrastructure, which resulted in some of the probes not being assigned any new measurements. Eventually, the affected probes ran out of measurement tasks. This bug affected about 30% of the probes approximately between Friday 23h and Sunday 12h (UTC). We apologise for any inconveniences this may cause. Regards, Robert Kisteleki RIPE Atlas team

1 0

New release in January, features you asked for...
by Vesna Manojlovic 01 Feb '13

01 Feb '13

Hi, we had a release 2 days ago, maybe you already noticed new features... * REST API -- althou in Beta! https://atlas.ripe.net/doc/rest * New costs for certain measurements: https://atlas.ripe.net/doc/credits & * 20 instead of 19 probes visualized in ping UDMs :) ... and if not, they are listed on RIPE Labs article: https://labs.ripe.net/Members/becha/ripe-atlas-january-2013-achievements ... and on the "announcements" page too: https://atlas.ripe.net/announce We are still working on "group access", and few more features are going to be announced to beta-testers soon. Share and enjoy! Regards, Vesna

4 4

2 probes down
by Jan Hugo Prins 23 Jan '13

23 Jan '13

Hello, This morning I got a notification that the probe in my datacentre is down. I checked everything and he looks just fine and is happily doing traffic. Then I noticed that the one behind my home fiber connection is also down, and that the starttime is about the same. Both of them at 6:56 this morning. Also checked that one and he is also doing traffic just fine. Houston, do we hava a problem? -- Met vriendelijke groet / Best regards, Jan Hugo Prins Infra and Isilon storage consultant E: jprins(a)betterbe.com T: +31-53-4800694 M: +31-6-26358951 S: jhaprins W: www.betterbe.com <http:///www.betterbe.com>

2 1

Thank you for making the 2012 a great year for RIPE Atlas!
by Vesna Manojlovic 16 Jan '13

16 Jan '13

Dear RIPE Atlas community, many thanks for hosting, testing & using RIPE Atlas! We have reached many milestones last year, and are looking forward to new challenges this year. Please see the story of the RIPE Atlas achievements in this RIPE Labs article: https://labs.ripe.net/Members/becha/ripe-atlas-2012-a-year-in-review Regards, Vesna -- Vesna Manojlovic BECHA(a)ripe.net Senior Community Builder @Ms_Measurements for Measurements Tools RIPE NCC http://ripe.net

1 0

Parametrization of UDM requests?
by Stephane Bortzmeyer 15 Jan '13

15 Jan '13

It seems that the parameters used for an UDM are the same for all probes. For instance, I would like to do a DNS UDM with a different question for each probe, something like "%p.mydomain.example" where %p would be replaced by the Probe ID. Is it possible? Or do you think it would be a worthwile improvment?

2 3

UI graphs
by nrw＠kaffeeschluerfer.com 10 Jan '13

10 Jan '13

On Tue Jan 8 08:15:44 CET 2013, Florian Bauhaus f.bauhaus at portrix-systems.de wrote: > On 01/07/13 22:57, Olaf Maunz wrote: > > The graphics for the pings seem to have vanished in the UI. At least for my account... > > > > If you open the ping UDM there is (at least for me) an tab that says 'RRDs' and there you have all the graphs. I think Olaf did not refer to the UI of the UDMs, but to the UI of the probes. At least for me as well, the graphs of the statistics started to show no data for a period starting sometime between Jan 5 and Jan 6, 2013. At some point, I got the message that there was some maintenance going on on the Atlas infrastructure side. However, nothing changed with respect to the graphs not showing current data once the maintenance was through. Interestingly, the graphs started showing something again for data collected starting as of about 8 AM UTC this morning. Apart from some interruptions due to my public IP address changing, my probe was considered "up" all the time, and I also saw it running its tests and getting responses to the various probe messages. However I still need to figure out (I am sure it is in the documentation, I just didn't get around to looking for the relevant parts yet) how to access the raw data for recent measurements to see whether that data not being displayed in the graphs was due to the collected data somehow not getting to the Atlas infrastructure for some reason (despite probe being considered up), or whether there was just an issue displaying the collected data. Has anyone else seen similar issues and/or some idea what might have happened? Thanks! Kind regards, Joachim

2 3