Re: [Nagios-devel] notification_interval check vs. check_period
Posted: Mon Sep 15, 2008 12:13 pm
------=_Part_16087_23765381.1221509612025
Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
On Sat, Sep 13, 2008 at 5:22 AM, Hendrik B=8A=E4cker wrote:
> Marcel schrieb:
> > If you have a service that would be checked every 10 seconds, and
> > notification interval =3D 60, then you should get the warning messa=
ge.
> >
> > I think a bit and that would not be the case, but instead, not 10
> > seconds, but like 300 (or five minutes if interval_length=3D1). Then th=
e
> > warning is issued.
>
> So, actual I'm a little bit confused about what is the fact.
>
> You have service object with check_interval =3D 300 (seconds, cause
> interval_length=3D1) and a notification_interval of 10 (seconds) or vice
> versa?
No, i have notification_interval's default value of 60 (minutes if
interval_length=3D60), but when using itnerval_length=3D1 and
normal_check_interval of 300 (seconds), then the warning message saying tha=
t
my notification interval is lower than my command_check_interval appears at
nagios.log
check_interval =3D 300 +
> notification_interval =3D 10
> The warning message is IMHO OK cause it's useless to resend notification
> cause of a service state that isn't able to change.
That's what Nagios thinks aswell.
Please drop us a short note what you are doing exactly.
>
Notification_interval never gets multiplied by interval_length (nor
divided), so it assumes interval_length =3D 60.
Documentation says notification_interval is "time units", but never gets
checked against interval_length, as command_check_interval is in line:
1344 command_check_interval*=3Dinterval_length;
notification_interval never gets multiplied by interval_length, at least at
config.c, then when using the default notification_interval of 60, and
setting a 300s normal_check_interval (five minutes, because
interval_length=3D1), then the sanity check at line 1878 prints the wrong
warning message.
My solution was to multiply (not assigning
notification_interval*=3Dinterval_length), in config.c at check time, but t=
hat
is wrong because it did not assign notification_interval*=3Dinterval_length=
,
as command_check_interval is.
Well, i did get rid of the wrong warning messages, but i think notification=
s
would be messed up (i did not get into notifications.c to confirm anything)=
.
Anyone seeing messed up notifications with interval_length On Sat, Sep 13, 2008 at 5:2=
2 AM, Hendrik B=8A=E4cker <[email protected]> wrote:
Marcel schrieb:
> If you have a service that would b=
e checked every 10 seconds, and
> notification interval =3D 60, then you should get the wa=
rning message.>
> I think a bit and that would not be the case, but instead, not 10
> seconds, but like 300 (or five minutes if interval_length=3D1). Then t=
he
> warning is issued.
So, actual I'm a little bit confused about what is the fact.
You have service object with check_interval =3D 300 (seconds, cause
interval_length=3D1) and a notification_interval of 10 (seconds) or vice
versa?No, i have notification_interval's default =
value of 60 (minutes if interval_length=3D60), but when using itnerval_leng=
th=3D1 and normal_check_interval of 300 (seconds), then the warning message=
saying that my notification interval is lower than my command_check_interv=
al appears at nagios.log
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid=
rgb(
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]
Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
On Sat, Sep 13, 2008 at 5:22 AM, Hendrik B=8A=E4cker wrote:
> Marcel schrieb:
> > If you have a service that would be checked every 10 seconds, and
> > notification interval =3D 60, then you should get the warning messa=
ge.
> >
> > I think a bit and that would not be the case, but instead, not 10
> > seconds, but like 300 (or five minutes if interval_length=3D1). Then th=
e
> > warning is issued.
>
> So, actual I'm a little bit confused about what is the fact.
>
> You have service object with check_interval =3D 300 (seconds, cause
> interval_length=3D1) and a notification_interval of 10 (seconds) or vice
> versa?
No, i have notification_interval's default value of 60 (minutes if
interval_length=3D60), but when using itnerval_length=3D1 and
normal_check_interval of 300 (seconds), then the warning message saying tha=
t
my notification interval is lower than my command_check_interval appears at
nagios.log
check_interval =3D 300 +
> notification_interval =3D 10
> The warning message is IMHO OK cause it's useless to resend notification
> cause of a service state that isn't able to change.
That's what Nagios thinks aswell.
Please drop us a short note what you are doing exactly.
>
Notification_interval never gets multiplied by interval_length (nor
divided), so it assumes interval_length =3D 60.
Documentation says notification_interval is "time units", but never gets
checked against interval_length, as command_check_interval is in line:
1344 command_check_interval*=3Dinterval_length;
notification_interval never gets multiplied by interval_length, at least at
config.c, then when using the default notification_interval of 60, and
setting a 300s normal_check_interval (five minutes, because
interval_length=3D1), then the sanity check at line 1878 prints the wrong
warning message.
My solution was to multiply (not assigning
notification_interval*=3Dinterval_length), in config.c at check time, but t=
hat
is wrong because it did not assign notification_interval*=3Dinterval_length=
,
as command_check_interval is.
Well, i did get rid of the wrong warning messages, but i think notification=
s
would be messed up (i did not get into notifications.c to confirm anything)=
.
Anyone seeing messed up notifications with interval_length On Sat, Sep 13, 2008 at 5:2=
2 AM, Hendrik B=8A=E4cker <[email protected]> wrote:
Marcel schrieb:
> If you have a service that would b=
e checked every 10 seconds, and
> notification interval =3D 60, then you should get the wa=
rning message.>
> I think a bit and that would not be the case, but instead, not 10
> seconds, but like 300 (or five minutes if interval_length=3D1). Then t=
he
> warning is issued.
So, actual I'm a little bit confused about what is the fact.
You have service object with check_interval =3D 300 (seconds, cause
interval_length=3D1) and a notification_interval of 10 (seconds) or vice
versa?No, i have notification_interval's default =
value of 60 (minutes if interval_length=3D60), but when using itnerval_leng=
th=3D1 and normal_check_interval of 300 (seconds), then the warning message=
saying that my notification interval is lower than my command_check_interv=
al appears at nagios.log
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid=
rgb(
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]