Hi, On 9/11/24 2:24 PM, Gert Doering wrote:
I was wondering if it is possible to bring dis- and reconnect messages of RIPE Atlas probes more in line with each other. "In-Reply-To:" and/or "References:", please, so my MUA can nicely sort these together.
This might be harder, as you have to store message-id of original notification sent to each particular user in database. I think this is "stateless" now (just sending notification about status change).
The system knows when the probe disappeared, so has a timestamp that can be used to generate (togehter with the probe ID) a unique message ID which can be reconstructed on the second & further mails...
Since there is an connect/disconnect history in the web page, the system very likely already stores all necessary details :-)
If I look on message headers, notifications messages are sent from somewhat random workers. And worker hostname is now part of message id (sure, this can be changed to something more generic). I'm not saying it's not possible, but proper analysis needs to be performed. - Daniel
Gert Doering -- NetMaster