News for hackers. Stuff that matters.
Re:The quick website launch checklist by tingletech on Sunday August 14, 2011 @01:06PM (#2883971)
Sending an email on an error might be a bad idea. We had this set up on a server that powers an API (along with our main site). During a network problem in the data center where the server could not get to the mysql, we had about 10,000 requests on the sever = 10,000 emails = the outlook guys having to reboot the exchange server because of some odd interaction with their spam filtering appliance.
Re:The quick website launch checklist by troels on Sunday August 14, 2011 @01:50PM (#2884065)
I have a log that will mail me first time an error occurs. If it happens again, it will still be logged, but I don't get an email. Once I mark the error as resolved - if it happens again, I get an email.
Re:The quick website launch checklist by rtg on Sunday August 14, 2011 @05:24PM (#2884492)
Would you mind sharing how you set this up? That would actually make a great blog post.
Re:The quick website launch checklist by troels on Sunday August 14, 2011 @07:10PM (#2884776)
I'm afraid I'm too busy to blog at the moment, but the code is here: https://github.com/troelskn/fejlvarp
Re:The quick website launch checklist by tl on Sunday August 14, 2011 @01:30PM (#2884020)
We solve this by having the e-mails come out in hourly batches for errors, with a separate, single, immediate e-mail for "the site is down" type problems.