Module: check_mk Branch: master Commit: f163fcc6615e6218c29b2c3990050fe227ddaee7 URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=f163fcc6615e62… Author: Lars Michelsen <lm(a)mathias-kettner.de> Date: Tue Sep 20 15:39:13 2016 +0200 3886 Notifications that do not match any rule are sent to fallback mail / contacts When a notification is received and is not matched by any notification rule, it could be sent to a globally configured and optional fallback email address. So, if you did not configure this fallback email address, it was possible that generated notifications, e.g. from the Event Console, were not sent to any user. This has been extended so that you can either configure the global mail address or set and attribute for your user accounts individually. For each of your users you can now set the flag "Receive fallback notifications". Another change: If you use the rule based notifications and have not configured any fallback contact (either globally or user), there will be a warning message displayed on the notification configuration page. Another change: When having a notification rule that has a condition on contact groups, or any user creates a custom notification rule, and a notification was generated which had no contact group information at all, the notification was sent to ALL users, instead of none. That was implemented this way just to be sure that the notifications are not suppressed by accident. This has been changed to be also processed like other notifications that do not match any rule. Finally these notifications will be handled with the configured fallback contacts. --- .werks/3886 | 31 ++++++++++++++++++++ ChangeLog | 1 + modules/events.py | 6 ++-- modules/notify.py | 32 +++++++++++++++----- web/htdocs/wato.py | 50 +++++++++++++++++++++++++------- web/plugins/wato/globals_notification.py | 3 +- 6 files changed, 101 insertions(+), 22 deletions(-) Diff: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commitdiff;h=f163fcc661…