After taking a closer look at crashmailmatch, I think I'm going to just do my documentation fixes to crashmail, and leave it at that... crashmailbatch does things in a _much_ cleaner way, although it might be nice to rework crashmail as a derivative of it that just doesn't use batching... Since most of the actual email functionality is pulled out into the separate ProcessStateEmailMonitor class, it shouldn't be difficult to use that as a base, and just disable batching.
On Wed, Dec 8, 2010 at 11:36, Jason Koppe <jko...@indeed.com> wrote: > Awesome ideas. > > > On Wed, Dec 8, 2010 at 11:24, Roger Hoover <roger.hoo...@gmail.com> wrote: > >> I think that's a good idea and for what it's worth, that's what >> crashmailbatch does, not only for the reason you mentioned but also >> b/c forking a process per alert can be very CPU intensive. >> >> Cheers, >> >> Roger >> >> On Wed, Dec 8, 2010 at 9:22 AM, David Bronke <whitel...@gmail.com> wrote: >> > Also, I had another idea for an enhancement to crashmail... I don't >> > generally install sendmail on any of my machines, because it tends to be >> too >> > much of a pain to set up. Instead, I coded a simple email notification >> > module in Python a while ago using the smtplib module, and we've been >> using >> > it on all the servers at my company for about a year now. The meat of it >> is >> > only about 10 lines of code, and I could easily stick that into >> crashmail as >> > a default method of sending emails, while keeping support for custom >> > sendmail commands for those who use them. Also, this would allow us to >> > specify the 'from' address directly in crashmail instead of having to >> use >> > sendmail's command line to do that. >> > >> > On Tue, Dec 7, 2010 at 17:37, Roger Hoover <roger.hoo...@gmail.com> >> wrote: >> >> >> >> FYI, I recently added a program to superlance called crashmailbatch >> >> which will batch up alerts during a time interval instead of sending >> >> an email for each one. >> >> >> >> On Tue, Dec 7, 2010 at 3:10 PM, David Bronke <whitel...@gmail.com> >> wrote: >> >> > Cool, thanks! I'm working on a patch for a few minor things in >> crashmail >> >> > (unused variables, incorrect references to the file being 'httpok', >> and >> >> > some >> >> > other doc fixes) and to the README; I'll post it when I've completed >> it. >> >> > >> >> > >> >> > On Tue, Dec 7, 2010 at 16:08, Jason Koppe <jko...@indeed.com> wrote: >> >> >> >> >> >> Here's what I use. crashmail notifies notify-on-crash (-m) when any >> >> >> child >> >> >> process exits unexpectedly (-a) and adds the hostname to the subject >> >> >> line >> >> >> (-o). I set the from address with sendmail so it is consistent >> across >> >> >> all >> >> >> of my environments and makes it through my mail provider. >> >> >> >> >> >> [eventlistener:crashmail] >> >> >> command=/usr/bin/crashmail -o hostname -a -m >> notify-on-cr...@domain.com >> >> >> -s >> >> >> '/usr/sbin/sendmail -t -i -f crash-notif...@domain.com' ; the >> program >> >> >> (relative uses PATH, can take args) >> >> >> events=PROCESS_STATE ; event notif. types to subscribe to >> >> >> (req'd) >> >> >> >> >> >> >> >> >> >> environment=SUPERVISOR_USERNAME='admin',SUPERVISOR_PASSWORD='password',SUPERVISOR_SERVER_URL=' >> http://hostname:9001' >> >> >> ; process environment additions >> >> >> >> >> >> >> >> >> On Tue, Dec 7, 2010 at 15:53, David Bronke <whitel...@gmail.com> >> wrote: >> >> >>> >> >> >>> The documentation for crashmail seems to be nearly nonexistent, and >> >> >>> I'm >> >> >>> confused as to how to use it... The only docs I can find are in the >> >> >>> script >> >> >>> itself, but the command listed in the example supervisord config >> >> >>> section is >> >> >>> for paster, not crashmail. Is this actually the correct command to >> >> >>> use? If >> >> >>> so, what should the contents of 'myserve.ini' be? >> >> >>> I'd like to figure out how to use all the superlance plugins so the >> >> >>> current README.txt can be updated... once I've worked through all >> the >> >> >>> issues >> >> >>> I find, I'll submit a patch. >> >> >>> Thanks! >> >> >>> _______________________________________________ >> >> >>> Supervisor-users mailing list >> >> >>> Supervisor-users@lists.supervisord.org >> >> >>> http://lists.supervisord.org/mailman/listinfo/supervisor-users >> >> >>> >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> >> Jason Koppe >> >> >> jko...@indeed.com >> >> >> (210) 445-8242 >> >> > >> >> > >> >> > _______________________________________________ >> >> > Supervisor-users mailing list >> >> > Supervisor-users@lists.supervisord.org >> >> > http://lists.supervisord.org/mailman/listinfo/supervisor-users >> >> > >> >> > >> > >> > >> > > > > -- > Jason Koppe > jko...@indeed.com > (210) 445-8242 >
_______________________________________________ Supervisor-users mailing list Supervisor-users@lists.supervisord.org http://lists.supervisord.org/mailman/listinfo/supervisor-users
