On Tue, 4 Jan 2022 at 09:36, Stephen J. Turnbull <stephenjturnbull@gmail.com> wrote:
Philip Colmer writes:
For the MM3 servers, we're probing "/mailman3/lists/".
You could create a path in urls.py called "250" that does nothing but respond with a 250 status (and maybe a hello-world page). The issue with /mailman3/lists/ is that it queries core for the lists (which, if successful, proves that core is up as a side effect).
Is there another URL we could use to check the health of a MM3 server
What does this mean to you? Our Mailman 3 suite consists of three applications, core, Postorius, and HyperKitty, which might or might not be installed, and if installed might or might not be running on the same host. Core in turn depends on the MTA and starts a bunch of qrunners. Any of the above might fall over on its own. (I don't think there's any way to check on the health of a particular qrunner from the net, though.)
That's a very good point. It would be nice if, at some point, an actual healthcheck endpoint could be included that returned some information about the state of the different applications as a JSON blob. It is increasingly useful to try and spot application problems before users do :)
Or, if not, is there a way of stopping Django from sending out the emails?
There probably is, but I don't know it. Mark might, but if not asking on a Django list would be a better place.
Thank you.
Regards
Philip