email-deliverability, GitLab, observability, Open Source, platform engineering One thing that doesn’t get enough attention in platform engineering is email deliverability. Not whether the email looks good, but whether it arrives at all — and how fast. At GitLab, emails are part of the critical path in more ways than one. Issue notifications go out via Mailgun. So do new user registration confirmation emails. Same infrastructure, same components. If one is slow, the other probably is too. That connection isn’t obvious until you think about it, but once you do, it’s the kind of thing you want a monitor for. So I built one. issue-to-email-monitor does exactly what it sounds like. It creates a GitLab issue in a configured project, then polls a dedicated Gmail address via POP3, waiting for the notification email to arrive. If the email lands within 300 seconds, success. If not, failure. Either way, it cleans up after itself by deleting the issue. It runs on a loop — create, wait, log,…
No comments yet. Log in to reply on the Fediverse. Comments will appear here.