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] [Feature Request] Show probe address on failure notifications

Previous message (by thread): [atlas] New on RIPE Labs: Researching F-root Anycast Placement Using RIPE Atlas
Next message (by thread): [atlas] [Feature Request] Show probe address on failure notifications

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Brian Rak brak at gameservers.com
Fri Oct 16 01:08:02 CEST 2015

I recently received one an email indicating one of my probes is offline:

This is the second reminder that your probe (#20689 ) is not connected 
to our infrastructure and has been disconnected since 2015-09-14 09:37 
UTC. Could you please check whether everything is set up correctly on 
your side? If it is, and your probe is still reported as disconnected 
when you log in at https://atlas.ripe.net, please reply to this email so 
that we can follow up.

Is there any way these can be modified to include further information 
(like the probe's address, or basically anything about it)?  Probe 20689 
means nothing to me, so I have to log in to take a look at exactly what 
it is, and where I need to go to fix it.

Previous message (by thread): [atlas] New on RIPE Labs: Researching F-root Anycast Placement Using RIPE Atlas
Next message (by thread): [atlas] [Feature Request] Show probe address on failure notifications

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ ripe-atlas Archives ]