I asked this question on both mailing list in the past. Can someone point out why we chose to ignore flapping option in hostescalation and serviceescalation? Thanks<br><br><div class="gmail_quote">On Thu, Nov 19, 2009 at 9:43 PM, Mark Gius <span dir="ltr"><<a href="mailto:mgius@createspace.com">mgius@createspace.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">Hendrik Baecker wrote:<br>
> -----BEGIN PGP SIGNED MESSAGE-----<br>
> Hash: SHA1<br>
><br>
> Am 18.11.09 01:02, schrieb Mark Gius:<br>
><br>
>> The patch adds 4 configuration directives to service escalations<br>
>> definitions:<br>
>><br>
>> first_warning_notification #<br>
>> last_warning_notification #<br>
>> first_critical_notification #<br>
>> last_critical_notification #<br>
>><br>
>> Behavior is identical to (first|last)_notification, except that they<br>
>> check against the count of warning/critical notifications instead of the<br>
>> number of total notifications.<br>
>><br>
><br>
> Hi,<br>
><br>
> I really like this but what about unknown state notifications which<br>
> might be used?<br>
><br>
</div>I thought of unknowns right after I sent the patch. We don't really use<br>
them in our deployment, so I wasn't thinking about them during<br>
implementation. It's easy enough to add.<br>
<div class="im">> What about hostescalations? Would you patch them too?<br>
><br>
</div>I was going to question the usefulness of this, but they can be both<br>
"down" and "unreachable." I'll get an updated patch up sometime next week.<br>
<br>
I'd like some feedback on how I modified the CGIs to display the new<br>
variables. I was hesitant to add a bunch more columns to that table,<br>
considering it's already pretty large, so I just put all 4 of the new<br>
thresholds in the same table entry (all, warn, crit, unknown). Putting<br>
all of the thresholds in the same column is unclear without reading the<br>
source. I can add new table columns if that's the "proper" thing to<br>
do. Or if somebody has a solution I'm not thinking of I'd love for the<br>
config output to be very clear.<br>
<font color="#888888"><br>
-Gius<br>
</font><div><div></div><div class="h5"><br>
------------------------------------------------------------------------------<br>
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day<br>
trial. Simplify your report design, integration and deployment - and focus on<br>
what you do best, core application coding. Discover what's new with<br>
Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_blank">http://p.sf.net/sfu/bobj-july</a><br>
_______________________________________________<br>
Nagios-devel mailing list<br>
<a href="mailto:Nagios-devel@lists.sourceforge.net">Nagios-devel@lists.sourceforge.net</a><br>
<a href="https://lists.sourceforge.net/lists/listinfo/nagios-devel" target="_blank">https://lists.sourceforge.net/lists/listinfo/nagios-devel</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Cordially,<br>Shadhin Rahman<br>