Re: [atlas] Notify time setting does not work
Hi, On Fri, Aug 18, 2017 at 01:01:48PM +0200, Viktor Naumov wrote: > Here how it (always) works. > > There is a job started every 30 minutes. If a probe is down longer than > the "Notify time" you will get a notification. So in your case (10 > minutes) you should get an email within interval of [10 , 40) minutes. This is a bit awkward... can this be improved, like, run this job every minute or so? A single "select id from probes where downtime>notify and not is_notified" statement shouldn't cost much... (no ideas about your table setup, though :-) ) Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AGVorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 signature.asc Description: PGP signature
Re: [atlas] Notify time setting does not work
Hi Marat, Here how it (always) works. There is a job started every 30 minutes. If a probe is down longer than the "Notify time" you will get a notification. So in your case (10 minutes) you should get an email within interval of [10 , 40) minutes. wbr /vty On 8/17/17 9:15 AM, Marat Khalili wrote: Probes have very handy feature of sending a notification when the probe is disconnected. I have mine set to 10 minutes, however last two such notifications only arrived 30 minutes after the probe was disconnected. Probe #26656 if that's important. One would think that probe itself was slow to react, but last time I monitored outage from the very beginning and the probe's page correctly showed "Disconnected for: 1 minute" and so on. Neither it is a case of slow email arrival, since according to Received header in the email it was indeed received from worker1.atlas.ripe.net 30+ minutes after disconnection time mentioned in the email body. Can it be that "Notify time" setting just doesn't work and some default value of 30 minutes is used? -- With Best Regards, Marat Khalili
Re: [atlas] Notify time setting does not work
On 17.08.2017 13:34, Marat Khalili wrote: > But: > >> Your probe 26656 has been disconnected from the RIPE Atlas >> infrastructure since 2017-08-16 08:58:54 UTC > What happened between 08:58:54 UTC and 09:30:00 +? Erm, yes... Didn't check the mail body. Sorry, my bad. So it appears that this indeed *IS* onyl to the Atlas team @ NCC to answer. Cheers, -C.
