Module: check_mk
Branch: master
Commit: c5a953b98fda986c3decaa2243c702663a03038f
URL:
http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=c5a953b98fda98…
Author: Sven Rueß <sr(a)mathias-kettner.de>
Date: Wed Jul 5 14:13:26 2017 +0200
new bug related to mknotify with distributed monitoring
Change-Id: I1f7d9e8751b18df74e79cf70d276b10a824cc862
---
.bugs/2927 | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/.bugs/2927 b/.bugs/2927
new file mode 100644
index 0000000..b4c6228
--- /dev/null
+++ b/.bugs/2927
@@ -0,0 +1,12 @@
+Title: mknotify with distributed monitoring
+Component: wato
+State: open
+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.