When I restart processes via "sudo god restart process", sometimes I get emails about the process being unavailable. My guess is that god is still checking to see if it's up, and if it checks right after it stops the process, it tells me it's down. I don't have any hard data to back this up, but I think it's a pretty good guess. Anyways, I know it seems trivial, but it's my #1 complaint about monitoring software - they treat your inbox/im/sms/whatever like you're just itching to have notifications rammed down your internet tubes. I really don't want to be notified when logrotate restarts processes, or when another developer is doing a deploy. When I get a message, I should think "oh shit" not "shut up". In other words, the power of monitoring software is negated when you get accustomed to ignoring it all the time.
I know this is pretty ranty, but I just moved away from monit for this exact reason. I now have God all set up in my staging cluster, and during testing I keep getting notified that one or two mongrels is/are down when I trigger the restart. I'm perfectly willing to figure this out myself, but could you provide some guidance Tom? I looked in the source and I could hack something together, but it probably wouldn't be as good as if I got your opinion first. If the author of the software were to start to address this, where would he start... -Woody (I noticed the lack of activity on the forums lately - I'm sure you're busy with github, so good luck with that; it's ridiculously awesome) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "god.rb" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/god-rb?hl=en -~----------~----~----~----~------~----~------~--~---
