Nagios Support Forum

--0003255550f20c531c0478cfdc63
Content-Type: text/plain; charset=ISO-8859-1

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

On Thu, Nov 19, 2009 at 9:43 PM, Mark Gius wrote:

> Hendrik Baecker wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Am 18.11.09 01:02, schrieb Mark Gius:
> >
> >> The patch adds 4 configuration directives to service escalations
> >> definitions:
> >>
> >> first_warning_notification #
> >> last_warning_notification #
> >> first_critical_notification #
> >> last_critical_notification #
> >>
> >> Behavior is identical to (first|last)_notification, except that they
> >> check against the count of warning/critical notifications instead of the
> >> number of total notifications.
> >>
> >
> > Hi,
> >
> > I really like this but what about unknown state notifications which
> > might be used?
> >
> I thought of unknowns right after I sent the patch. We don't really use
> them in our deployment, so I wasn't thinking about them during
> implementation. It's easy enough to add.
> > What about hostescalations? Would you patch them too?
> >
> I was going to question the usefulness of this, but they can be both
> "down" and "unreachable." I'll get an updated patch up sometime next week.
>
> I'd like some feedback on how I modified the CGIs to display the new
> variables. I was hesitant to add a bunch more columns to that table,
> considering it's already pretty large, so I just put all 4 of the new
> thresholds in the same table entry (all, warn, crit, unknown). Putting
> all of the thresholds in the same column is unclear without reading the
> source. I can add new table columns if that's the "proper" thing to
> do. Or if somebody has a solution I'm not thinking of I'd love for the
> config output to be very clear.
>
> -Gius
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus
> on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now. http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Nagios-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/lis ... gios-devel
>



--
Cordially,
Shadhin Rahman

--0003255550f20c531c0478cfdc63
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I asked this question on both mailing list in the past.=A0 Can someone poin=
t out why we chose to ignore flapping option in hostescalation and servicee=
scalation?=A0 ThanksOn Thu, Nov 19, 2009=
at 9:43 PM, Mark Gius <[email protected]> wrote:
Hendrik Baecker wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Am 18.11.09 01:02, schrieb Mark Gius:
>
>> The patch adds 4 configuration directives to service escalations
>> definitions:
>>
>> =A0 =A0first_warning_notification #
>> =A0 =A0last_warning_notification #
>> =A0 =A0first_critical_notification #
>> =A0 =A0last_critical_notification #
>>
>> Behavior is identical to (first|last)_notification, except that th=
ey
>> check against the count of warning/critical notifications instead =
of the
>> number of total notifications.
>>
>
> Hi,
>
> I really like this but what about unknown state notifications which
> might be used?
>
I thought of unknowns right after I sent the patch. =A0We don'

...[email truncated]...


This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]