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] New on RIPE Labs: Processing RIPE Atlas Results with jq
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Gert Doering
gert at space.net
Fri Aug 18 14:03:43 CEST 2017
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 AG Vorstand: 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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: </ripe/mail/archives/ripe-atlas/attachments/20170818/8972f9e2/attachment.sig>
- Previous message (by thread): [atlas] Notify time setting does not work
- Next message (by thread): [atlas] New on RIPE Labs: Processing RIPE Atlas Results with jq
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]