Re: [Nagios-devel] Bug?: Custom notifications ignore
Posted: Mon Aug 01, 2011 5:38 pm
On 08/01/2011 08:10 PM, Paul M. Dubuc wrote:
> Thanks for the response. I'm still puzzled, thought. If it makes sense
> to override the regular notification logic for custom notifications,
> what is the point of having the Broadcast option?
To re-quote the doc from your initial request:
> "Custom notifications normally follow the regular notification logic in=
=20
> Nagios. Selecting the Forced option will force the notification to be s=
ent=20
> out, regardless of the time restrictions, whether or not notifications =
are=20
> enabled, etc. Selecting the Broadcast option causes the notification to=
be=20
> sent out to all normal (non-escalated) and escalated contacts. These op=
tions=20
> allow you to override the normal notification logic if you need to get =
an=20
> important message out."
And if I may paraphrase
http://nagios.sourceforge.net/docs/3_0/ ... tions.html myself: The
available filters which control who might have a notification sent to
him are:
1. program-wide notification disable switch (not relevant here)
2. host/service-specific notification disable switch
3. downtime or flapping in effect
4. several notification_options
5. several notification_periods
6. first_notification_delay & notification_interval (not relevant here)
7. match of the # of the notification-to-be to the escalation rules
8. PROBLEM/RECOVERY matching (probably not relevant here)
According to the docs' wording - I never ran tests or inspected the code
yet, mind you -, "Forced" should override 2., 5., and some other
unspecified filters :-}, while "Broadcast" should override 7.. The
filter whose relevance we've been discussing is 4..
Kind regards,
J. Bern
--=20
Jochen Bern, Systemingenieur --- LINworks GmbH
Postfach 100121, 64201 Darmstadt | Robert-Koch-Str. 9, 64331 Weiterstadt
PGP (1024D/4096g) FP =3D D18B 41B1 16C0 11BA 7F8C DCF7 E1D5 FAF4 444E 1C2=
7
Tel. +49 6151 9067-231, Zentr. -0, Fax -299 - Amtsg. Darmstadt HRB 85202
Unternehmenssitz Weiterstadt, Gesch=E4ftsf=FChrer Metin Dogan, Oliver Mic=
hel
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]
> Thanks for the response. I'm still puzzled, thought. If it makes sense
> to override the regular notification logic for custom notifications,
> what is the point of having the Broadcast option?
To re-quote the doc from your initial request:
> "Custom notifications normally follow the regular notification logic in=
=20
> Nagios. Selecting the Forced option will force the notification to be s=
ent=20
> out, regardless of the time restrictions, whether or not notifications =
are=20
> enabled, etc. Selecting the Broadcast option causes the notification to=
be=20
> sent out to all normal (non-escalated) and escalated contacts. These op=
tions=20
> allow you to override the normal notification logic if you need to get =
an=20
> important message out."
And if I may paraphrase
http://nagios.sourceforge.net/docs/3_0/ ... tions.html myself: The
available filters which control who might have a notification sent to
him are:
1. program-wide notification disable switch (not relevant here)
2. host/service-specific notification disable switch
3. downtime or flapping in effect
4. several notification_options
5. several notification_periods
6. first_notification_delay & notification_interval (not relevant here)
7. match of the # of the notification-to-be to the escalation rules
8. PROBLEM/RECOVERY matching (probably not relevant here)
According to the docs' wording - I never ran tests or inspected the code
yet, mind you -, "Forced" should override 2., 5., and some other
unspecified filters :-}, while "Broadcast" should override 7.. The
filter whose relevance we've been discussing is 4..
Kind regards,
J. Bern
--=20
Jochen Bern, Systemingenieur --- LINworks GmbH
Postfach 100121, 64201 Darmstadt | Robert-Koch-Str. 9, 64331 Weiterstadt
PGP (1024D/4096g) FP =3D D18B 41B1 16C0 11BA 7F8C DCF7 E1D5 FAF4 444E 1C2=
7
Tel. +49 6151 9067-231, Zentr. -0, Fax -299 - Amtsg. Darmstadt HRB 85202
Unternehmenssitz Weiterstadt, Gesch=E4ftsf=FChrer Metin Dogan, Oliver Mic=
hel
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]