Branch: refs/heads/master
Home:
https://github.com/tribe29/checkmk
Commit: ee59b3e3a2308ae2fd038f5b22b464f83bef2d61
https://github.com/tribe29/checkmk/commit/ee59b3e3a2308ae2fd038f5b22b464f83…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2019-07-25 (Thu, 25 Jul 2019)
Changed paths:
M cmk/gui/plugins/wato/utils/simple_modes.py
Log Message:
-----------
DCD connection config: Improve titles and texts
Change-Id: I5d2bdd6f3ba1d7a1326c6f1266847d16db1d2280
Commit: 5c39daf1396a3260f42aa0cf3e89a054713cabb5
https://github.com/tribe29/checkmk/commit/5c39daf1396a3260f42aa0cf3e89a0547…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2019-07-25 (Thu, 25 Jul 2019)
Changed paths:
A .werks/7987
M omd/packages/mk-livestatus/LIVESTATUS_TCP_TLS
M omd/packages/mk-livestatus/skel/etc/mk-livestatus/xinetd.conf
M omd/packages/omd/omdlib/main.py
Log Message:
-----------
7987 FIX Fix xinetd.conf conflict on "omd mv/cp"
When performing an omd cp or omd mv to copy or rename a site, this resulted
in a conflict with the xinetd.conf configuration file of Livestatus, when
it was enabled to listen via TCP.
This issue affected all previous 1.6 releases.
CMK-2413
Change-Id: Ia523d439e0065ab53e8cc41790fa6e6132c54145
Commit: 326534cea6f9df83f5993228fe9e026d7656a342
https://github.com/tribe29/checkmk/commit/326534cea6f9df83f5993228fe9e026d7…
Author: Tom Baerwinkel <tom.baerwinkel(a)tribe29.com>
Date: 2019-07-25 (Thu, 25 Jul 2019)
Changed paths:
M cmk_base/notify.py
Log Message:
-----------
Refactoring of notify_bulk
The bulk_context now contains the context of the individual
notifications instead of the final output. This will be useful
When writing history log entries later on.
CMK-2079
Change-Id: Ia0ee3c583d33676f549c374280ed64edba03dd2f
Commit: 872ee857b3883ef4b7328c185b83b21f9e87b9a9
https://github.com/tribe29/checkmk/commit/872ee857b3883ef4b7328c185b83b21f9…
Author: Tom Baerwinkel <tom.baerwinkel(a)tribe29.com>
Date: 2019-07-25 (Thu, 25 Jul 2019)
Changed paths:
A .werks/8783
M cmk_base/notify.py
Log Message:
-----------
8783 FIX bulk notifications did not produce failed notifications
If a notification script returned a non-zero exit code and was
configured for bulk notifications no failed notifications were
shown in the GUI. With this fix one failed notification will
be produced for every notification present in the failed bulk.
Furthermore the view "Host and Service notifications" now shows
a "Final notification result" for every notification in a bulk.
CMK-2079
Change-Id: Ife79e17e6fb734cad8de11555c06d23ced8fb71f
Compare:
https://github.com/tribe29/checkmk/compare/25f99a4dc67b...872ee857b388