From: Jochen B. <Jochen.Bern@LINworks.de> - 2011-07-31 03:22:34
|
On 07/27/2011 11:00 PM, Paul M. Dubuc wrote: > I just discovered what looks like a possible bug in the "Send custom > host/service notification" command in Nagios 3.2.3. [...] The command > description says that "Custom notifications normally follow the regular > notification logic in Nagios. [...]" > I didn't use either the Forced or Broadcast option and the OK status > notification goes to contacts that have only 'c' (critical) or 'd' (down) for > their service/host_notification_options and escalation_options. Is this a > bug? Seems like this should only happen if the Broadcast option is checked. FWIW: Nagios suppresses regular OK/RECOVERY notifications unless the contact in question did get a notification for the preceding non-OK state. In your case, there *was no* preceding non-OK state, so if the analogy were taken *that* far, CUSTOM notifications for services in an OK state would *never* get sent. I don't think you'd want that. ;-) CUSTOM notifications carry the current state as additional information, not as their raison d'être - pretty much like FLAPPINGSTART and -STOP notifications. The reach of FLAPPING* notifications is controlled by their own notification_option, 'f'. It would certainly be possible to define a new notification_option for CUSTOM notifications, but unless you can restrict the semantics of such notifications to something narrower than "whatever the guy was thinking when he typed the gobbledygook into the comment field", I fail to see how a contact could be really sure that such notifications will never be relevant to him. Regards, J. Bern -- Jochen Bern, Systemingenieur --- LINworks GmbH <http://www.LINworks.de/> Postfach 100121, 64201 Darmstadt | Robert-Koch-Str. 9, 64331 Weiterstadt PGP (1024D/4096g) FP = D18B 41B1 16C0 11BA 7F8C DCF7 E1D5 FAF4 444E 1C27 Tel. +49 6151 9067-231, Zentr. -0, Fax -299 - Amtsg. Darmstadt HRB 85202 Unternehmenssitz Weiterstadt, Geschäftsführer Metin Dogan, Oliver Michel |