Page MenuHomePhabricator

Setup monitoring for mailman3
Closed, ResolvedPublic

Description

We can copy most of the checks from mailman2, but we should also verify all the individual mailman3 services (hyperkitty, mailman-web, mailman) are all running.

Event Timeline

Change 675078 had a related patch set uploaded (by Legoktm; author: Legoktm):
[operations/puppet@production] mailman3: Add basic monitoring for SMTP (exim) and HTTPS (apache/django)

https://gerrit.wikimedia.org/r/675078

Change 675078 merged by Legoktm:
[operations/puppet@production] mailman3: Add basic monitoring for SMTP (exim) and HTTPS (apache/django)

https://gerrit.wikimedia.org/r/675078

jijiki triaged this task as Medium priority.Mar 29 2021, 9:00 PM

Change 681289 had a related patch set uploaded (by Legoktm; author: Legoktm):

[operations/puppet@production] lists: Use check_mailman_queue for monitoring mailman3 too

https://gerrit.wikimedia.org/r/681289

Change 681290 had a related patch set uploaded (by Legoktm; author: Legoktm):

[operations/puppet@production] mailman3: Send queue lengths to prometheus

https://gerrit.wikimedia.org/r/681290

Change 681289 merged by Legoktm:

[operations/puppet@production] lists: Use check_mailman_queue for monitoring mailman3 too

https://gerrit.wikimedia.org/r/681289

Change 681290 merged by Legoktm:

[operations/puppet@production] mailman3: Send queue lengths to prometheus

https://gerrit.wikimedia.org/r/681290

Legoktm claimed this task.

I think we're mostly good here.

https://grafana.wikimedia.org/d/GvuAmuuGk/mailman3?orgId=1 has the lists-next queue sizes but eventually I'll just edit the existing mailman dashboard to look at the mm3 paths.