Module: check_mk Branch: master Commit: 9cbdc9c3592b0b5cc414fc98d552e0a612facb1b URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=9cbdc9c3592b0b… Author: Mathias Kettner &lt;mk(a)mathias-kettner.de&gt; Date: Wed Mar 19 15:24:07 2014 +0100 Allow to restrict visibility of events by their host contacts The Event Console has now two new permissions: <ol> <li>See all events</li> <li>See events not related to a known host</li> </ol> Both permissions default to <i>yes</i> in all roles. If you remove the <i>See all events</i> permission then a user can only see events for hosts that either he is a monitoring contact for or that are not known to the monitoring at all (i.e. no host with such a name or IP address is configured as monitored host in your monitoring core). The visibility of the later ones can be switched off with the second permission. The second permission is only relevant if <i>See all events</i> is set to <i>no</i> - of course. Furthermore you can now assign <i>Fallback Contact Groups</i> to an event. This is done with a new rule option in the section <i>Outcome &amp; Action</i>. As soon as you assign contact groups these will be assumed for all hosts that are not in the monitoring. That groups will be attached as an additional information to each event created with that rule. These events will then be handled like as if the host is known to the monitoring when it comes to the visibility. --- .werks/749 | 27 +++++++++ ChangeLog | 1 + mkeventd/bin/mkeventd | 95 ++++++++++++++++------------- mkeventd/web/plugins/views/mkeventd.py | 104 +++++++++++++++++++++++++++++++- mkeventd/web/plugins/wato/mkeventd.py | 23 ++++++- web/htdocs/wato.py | 2 +- 6 files changed, 204 insertions(+), 48 deletions(-) Diff: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commitdiff;h=9cbdc9c359…