Planned Atlas downtime on 29 January
Dear RIPE Atlas users, Please be aware that we plan to do maintenance work in the RIPE Atlas core infrastructure two weeks from now, on Wednesday 29 January, between 9:00-12:00 CET (Amsterdam time). The RIPE Atlas website, UI and API will be unavailable in this period. The probes should remain connected and results will be collected normally, although during this period they can only be accessed real-time via the streaming service. Apologies for the inconvenience this may cause. Regards, Robert Kisteleki
On 2020-01-15 15:26, Robert Kisteleki wrote:
Dear RIPE Atlas users,
Please be aware that we plan to do maintenance work in the RIPE Atlas core infrastructure two weeks from now, on Wednesday 29 January, between 9:00-12:00 CET (Amsterdam time). The RIPE Atlas website, UI and API will be unavailable in this period. The probes should remain connected and results will be collected normally, although during this period they can only be accessed real-time via the streaming service.
Apologies for the inconvenience this may cause.
Regards, Robert Kisteleki
Dear All, This work has just started. Regards, Robert
On 2020-01-29 09:18, Robert Kisteleki wrote:
On 2020-01-15 15:26, Robert Kisteleki wrote:
Dear RIPE Atlas users,
Please be aware that we plan to do maintenance work in the RIPE Atlas core infrastructure two weeks from now, on Wednesday 29 January, between 9:00-12:00 CET (Amsterdam time). The RIPE Atlas website, UI and API will be unavailable in this period. The probes should remain connected and results will be collected normally, although during this period they can only be accessed real-time via the streaming service.
Apologies for the inconvenience this may cause.
Regards, Robert Kisteleki
Dear All,
This work has just started.
Regards, Robert
This work has finished. Even though we're closely monitoring the system's behaviour, please let us know if you encounter unexpected errors. Regards, Robert
Hi, I wanted to look at the log file of one of the built-in measurements this morning. Never mind the pretty printing, but I found that CSVQ [1] which I use for a lot of things can read JSON :=-)-O Given a log file "atlas.json" and executing csvq -i JSON allows (line separation for readability) SELECT ROUND(AVG(`avg`),4) AS Average, \ COUNT(*) AS Records \ FROM JSON_TABLE('{}',atlas); which results in something like +---------+---------+ | Average | Records | +---------+---------+ | 0.5673 | 9556 | +---------+---------+ I also find that the jsonlite library of R allows reading of the same file. Probably not news to anyone, but I found it kind of cool. greetings, el [1] https://github.com/mithrandie/csvq -- Dr. Eberhard W. Lisse \ / Obstetrician & Gynaecologist el@lisse.NA / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 \ / Bachbrecht 10007, Namibia ;____/
participants (2)
-
Dr Eberhard W Lisse -
Robert Kisteleki