<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=windows-1255">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7651.59">
<TITLE>RE: [Nagiosplug-help] Alerts flakey</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>I understand everthing about the definitions and dependencies. All that is fine.<BR>
<BR>
Explain to me more about paging for hosts.<BR>
The alerts that didn't come were hosts not responding critical warnings.<BR>
But the critical warnings were service warnings.<BR>
Also, why can't you warn for critical host warnings?<BR>
I noticed that is not an option. I don't understand that.<BR>
It WAS working, BTW.. I think as one person suggested, it's flakiness of the service and not configuration.<BR>
<BR>
<BR>
-----הודעה מקורית-----<BR>
מאת: Thomas Guyot-Sionnest [<A HREF="mailto:dermoth@aei.ca">mailto:dermoth@aei.ca</A>]<BR>
נשלח: ד 07/03/2007 08:06<BR>
אל: Ezra Radoff<BR>
עותק לידיעה: nagiosplug-help@lists.sourceforge.net<BR>
נושא: Re: [Nagiosplug-help] Alerts flakey<BR>
<BR>
On 07/03/07 08:33 AM, Ezra Radoff wrote:<BR>
><BR>
> They're not in the log. They're not running notifcations for critical<BR>
> events, just warnings.<BR>
<BR>
You should check all notification criteria and timeperiods from the<BR>
services down to the contact. One omition in between can block<BR>
notifications.<BR>
<BR>
Also take into account depedencies. If the host is down and you don't<BR>
page for hosts you will not receive anything. Also if a host in the path<BR>
is down it might stop notification for upstream hosts/services.<BR>
<BR>
Thomas<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>