Hi Lukas, Internally we refer to these probes as not-reporting and I agree that a notification would be useful.
These would then be sent if the probe: - does not have system-ipv4-works AND system-ipv6-works tags - does have a system-ipv4-doesnt-work OR system-ipv6-doesnt-work tag Question is if these emails should be send again after for instance 24 hours or a week or? As I am working on emails lately, I will add this notification to my list. Cheers, Johan On Mon, 25 Aug 2025 at 11:47, Lukas Tribus <[email protected]> wrote: > Hello, > > currently notifications are configurable for the event when a probe is > disconnected; however when a probes remains connected but stops > working (loosing or no having either system-ipv4-works and > system-ipv6-works tags), we are blind. > > I have written a monitor script to query the API for this, to get this > notification but I'm wondering if it would be possible to implement > this at RIPE. The system-<AF>-works tags are already there. > > Software bugs and I guess HW issues can trigger hung probes that > remain connected. It's hard to find out, unless one is specifically > looking for it or specifically expecting the result of a single probe > in a measurement. > > > > Lukas > ----- > To unsubscribe from this mailing list or change your subscription options, > please visit: https://mailman.ripe.net/mailman3/lists/ripe-atlas.ripe.net/ > As we have migrated to Mailman 3, you will need to create an account with > the email matching your subscription before you can change your settings. > More details at: https://www.ripe.net/membership/mail/mailman-3-migration/ >
----- To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/ripe-atlas.ripe.net/ As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
