Develop email-in tracer tool
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
KARL3 |
Fix Released
|
Medium
|
Christian Zagrodnick |
Bug Description
We don't have a reliable way to know when email-in is wedged. Rather than trying to monitor each part of the end-to-end facility, we should instead monitor the failure of a tracer email to be received.
The idea is that something, somewhere (hopefully inside the OSF NYC LAN) sends a tracer email to KARL every N minutes. This won't be a blog entry, as we don't want some dummy blog filling up and the content feeds getting blasted.
Instead, we'll develop a new tool, either as part of a community or something hanging off the top. This tool will record receipt of the email. We'll also make sure that if the tracer wasn't received in the last N minutes, monitoring gets triggered.
Some notes:
- Exercise as much of the machinery as possible. We don't really need to test the ability to create a blog entry or blog comment. If it goes out of the NYC network, through the Internets tubes, into the outer Postfix, through its spam filters, to the inner, through repoze.postoffice, and is picked up by the daemon, that will handle 99% of the problems.
- Make sure admins like Robert/Nat/Paul can go and see something about the tracer. Most likely the admin screen.
- Document, in that tool, the email address that is used for the To: on the tracer. That lets people send the email manually if they want to.
Changed in karl3: | |
milestone: | m55 → m54 |
Changed in karl3: | |
milestone: | m54 → m55 |
Changed in karl3: | |
milestone: | m55 → m56 |
tags: | added: r3.62 |
A very easy thing to check is a file age. So if a file like "tracer- last-receveid" was touched when the tracer is received the nagios check would be very simple.