Module: check_mk
Branch: master
Commit: 1a2edebb34d110b795e3019c6f819dfe348506f9
URL:
http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=1a2edebb34d110…
Author: Lars Michelsen <lm(a)mathias-kettner.de>
Date: Tue Jul 11 16:59:36 2017 +0200
Updated bug entries #2927
Change-Id: Id802dd54639f6b2bf657e6cc3fca0e82fff0172f
---
.bugs/2927 | 12 ++++++++++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/.bugs/2927 b/.bugs/2927
index b4c6228..32e15be 100644
--- a/.bugs/2927
+++ b/.bugs/2927
@@ -1,12 +1,20 @@
Title: mknotify with distributed monitoring
Component: wato
-State: open
+Class: bug
+State: wontfix
Date: 2017-07-05 14:08:01
Targetversion: 1.4.0
-Class: bug
If you set up a distributed monitoring environment with a central notification instance
on master site.
After activating mknotifyd and activate the listener port on the master, this setting
will automatically
synchronized to all slave sites. A user have to modify each sitespecific global settings
to deactivate
the listener and add the connection to the master.
This global setting should not be synchronized to all slaves.
+
+2017-07-11 16:58:04: changed state open -> wontfix
+We have introduced the site specific globals for the local site. With this change it is
now possible
+to configure individual settings for the central site. The "global settings"
now act as what they
+are named: global defaults.
+
+The central site specific option to enable the port listener should be set in the central
site
+specific global settings.