On 27/07/07, Jim Avery <[EMAIL PROTECTED]> wrote: > I've been having a similar problem and have thought about the solution > but haven't gotten around to implementing it yet. Mark Powell's > suggestion to rely on the service check notification is absolutely > right when you want to ignore brief bounces or lost pings. I'm going > to do just that, but I will still have a host notification enabled > too... > > I'll configure things so that the on-call engineers get the ping > service notification rather than the host notification - they don't > want to know about servers briefly bounced. The host notifications > I'll send only to me by email so I will know the next day which > servers have bounced overnight. I'm hoping that will bring me the > best of both worlds.
For the record, I tried my variation of Mark's suggestion and it didn't work because I hadn't taken the trouble to understand it properly. If I leave host checks enabled (contrary to Mark's advice), then as soon as any service check fails, Nagios will try the host check which will fail too and will immediately set the service check to a HARD status. Mark's suggestion works because host checks are disabled. The possible down-side is that you don't then see hosts go down in Nagios as such. The host up/down status is important to me because it is used in the Nexsm status map display. I think unfortunately I'm going to use escalations instead, although it's going to be a bit messy. Cheers, Jim ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Nagios-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
