I, too, have not received a monthly Ambassador Report email since January of this year - I had assumed it was stopped for some reason. I'd like to receive them again, if possible. Given there are a handful of folks chiming in here stating they have not received emails, it makes me wonder if there was some issue when migrating to "the new system that activates the reports" you mentioned - perhaps something for the RIPE team to investigate? I'd personally like to start receiving these once again.
Q1: 1. Do you find the monthly ambassador report useful in its current format?
A1: (answering based on the last report I received, Jan of this year) Yes, slightly. I wish the report was formatted more nicely - I'm a visual person, and the report being completely unformatted text makes it much more difficult to process & digest.
Q2: 2. Are there specific parts of the report you find particularly helpful or relevant?
A2: I find the following helpful; (a) total number of probes I've received, (b) connection rate, (c) newly connected probes, if any, (d) total connected probes, (e) historical ambassador credits, (f) which events were attended, (g) which probes are disconnected. I find the following unhelpful; (A) the length of the reminder to tell probe hosts "You might want to remind your hosts who have not plugged in their probes or whose probes are disconnected and advise them on what steps to take to fix each issue here: <link>" (suggestion: "You might want to remind your hosts with disconnected probes what steps to take: <link>"), (B) the troubleshooting link that follows could have many more entries, IMO, (C) "You have no probes with known USB issues" - great, but its not useful to me then, so omit it. I'd only want to know if I have any that do have known issues, but otherwise omit this please, (D) no mention of what to do now that an ambassador has distributed all the probes they were given (there used to be a mention of what to do, but that seems to have gone away; is that intentional because RIPE no longer wants the Atlas network to grow? Is it because there is no longer hardware available? Is it because RIPE would prefer hosts use VMs instead? Is it just something that was accidentally removed?) (E) a second reminder, just above the 'probes that are disconnected', that states "You have no ambassador probes that are experiencing USB stick issues".
I also agree with Gavin, an "exception report" of sorts would be handy to have, too, depending on what information it provided, and how actionable it would be for ambassadors. More specifically, I'd like to get an "exception report" that contains (1) which probes were disconnected for a longer period of time (once they have been disconnected for longer than say 6 months), and (2) what I can do about them. For (2), I'd want there to be something actionable, and a way for me to 'dismiss / ignore' this probe in future "exception reports". For example, I gave a probe to a colleague years ago whose house burnt down, they are ok, however their probe is long gone - I don't want / need reminders about this probe ever again, as it no longer exists. If this was the only probe that would show up in the "exception report", I'd want a way to acknowledge "yes, I'm aware or I know something is wrong. please do not notify me of this probe being an 'exception' again."
Best,
Chris