This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] Notify time setting does not work
- Previous message (by thread): [atlas] Notify time setting does not work
- Next message (by thread): [atlas] Notify time setting does not work
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Viktor Naumov
vnaumov at ripe.net
Fri Aug 18 13:01:48 CEST 2017
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 > >
- Previous message (by thread): [atlas] Notify time setting does not work
- Next message (by thread): [atlas] Notify time setting does not work
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]