Re: [atlas] Probe operator notifications
For this purpose I use an online ping check service. Your probe need to have IPv6 or public IPv4 and ICMP be not blocked by a firewall to be able to respond pings from outside. To be exact, I use http://wedos.online that is run by one of the largest server-hosting company in the Czech Republic. It is free of charge. You can choose how often (1 minute or more) it will ping the probe and how many pings can be lost, then it sends both DOWN and UP notifications (email, Slack, Rocket chat) Cheers Jiri ______________________________________________________________
Od: "Ponikierski, Grzegorz" <gponikie@akamai.com> Komu: "Edward Lewis" <edlewisjr@cox.net>, "ripe-atlas@ripe.net" <ripe-atlas@ripe.net> Datum: 11.12.2020 12:16 Předmět: Re: [atlas] Probe operator notifications
+1 for 'your probe came back on-line'
Regards, Grzegorz
From: Edward Lewis <edlewisjr@cox.net> Date: Thursday 2020-12-10 at 22:32 To: "ripe-atlas@ripe.net" <ripe-atlas@ripe.net> Cc: Ed Lewis <edlewisjr@cox.net> Subject: [atlas] Probe operator notifications
(Seeing the thread about DNS intercepted probes reminded me to send this:)
For 5 or so years running I have a probe operating in my garage (behind my home’s NAT and using the ISP’s NXDOMAIN rewriting, non-DNSSEC handling recursive server) a run-of-the-mill home cable set up.
When I got my November report, it said I’d been down the last half of November. That was news to me. I then down'd/up’d it and it reconnected and seems to be on-line again.
I do get the “your probe went off-line” notices. I would like “your probe came back on-line” notices as well. If we had those, I may have noticed it stayed down after the last message I saw.
Ed
Hi, On Sat, Dec 12, 2020 at 09:03:54AM +0100, ripe@brite.cz wrote:
For this purpose I use an online ping check service. Your probe need to have IPv6 or public IPv4 and ICMP be not blocked by a firewall to be able to respond pings from outside.
This is not the point. Of course I could use our monitoring for that. The thing is "the system sends a DOWN report, but no UP report", and having to resort to external monitoring (which will not work for probes behind customer links with NAT) is quite lame. Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279
+one from me, asked that this functionality be added 5 years ago.
On 12 Dec 2020, at 09:55, Gert Doering <gert@space.net> wrote:
Hi,
On Sat, Dec 12, 2020 at 09:03:54AM +0100, ripe@brite.cz wrote:
For this purpose I use an online ping check service. Your probe need to have IPv6 or public IPv4 and ICMP be not blocked by a firewall to be able to respond pings from outside.
This is not the point. Of course I could use our monitoring for that.
The thing is "the system sends a DOWN report, but no UP report", and having to resort to external monitoring (which will not work for probes behind customer links with NAT) is quite lame.
Gert Doering -- NetMaster -- have you enabled IPv6 on something today...?
SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279
Another way is to setup a script listening at measurement id 7000. This logs all the probes connection/disconnection to RIPE controllers. Romain On 12/13/20 6:14 AM, Colin Johnston wrote:
+one from me, asked that this functionality be added 5 years ago.
On 12 Dec 2020, at 09:55, Gert Doering <gert@space.net> wrote:
Hi,
On Sat, Dec 12, 2020 at 09:03:54AM +0100, ripe@brite.cz wrote:
For this purpose I use an online ping check service. Your probe need to have IPv6 or public IPv4 and ICMP be not blocked by a firewall to be able to respond pings from outside.
This is not the point. Of course I could use our monitoring for that.
The thing is "the system sends a DOWN report, but no UP report", and having to resort to external monitoring (which will not work for probes behind customer links with NAT) is quite lame.
Gert Doering -- NetMaster -- have you enabled IPv6 on something today...?
SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279
Another way is to setup a script listening at measurement id 7000. This logs all the probes connection/disconnection to RIPE controllers.
does that not put a disproportionate load on central servers just to tell me if my one probe is up or down? randy
participants (5)
-
Colin Johnston -
Gert Doering -
Randy Bush -
ripe＠brite.cz -
Romain Fontugne