Branch: refs/heads/1.6.0
Home:
https://github.com/tribe29/checkmk
Commit: ed39f288fa44e86cccee3784d5d6d7c5d1d40252
https://github.com/tribe29/checkmk/commit/ed39f288fa44e86cccee3784d5d6d7c5d…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2019-09-23 (Mon, 23 Sep 2019)
Changed paths:
A .werks/10173
M cmk_base/automations/check_mk.py
Log Message:
-----------
10173 FIX Host diagnose: Agent status was shown green even in case of errors
Change-Id: I556095f6b54b9ec4f40fad403fd117d3f2b5166f
Commit: 31c2dceb71096c6c480bff9e898e7b9ffd1f7e7b
https://github.com/tribe29/checkmk/commit/31c2dceb71096c6c480bff9e898e7b9ff…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2019-09-23 (Mon, 23 Sep 2019)
Changed paths:
M cmk_base/config.py
M cmk_base/core_nagios.py
M tests/unit/cmk_base/test_config.py
Log Message:
-----------
Centralize service discovery service name and conditional logic
Change-Id: Id3654bc3db6532eac45acd56d94f5be84045f2b9
Commit: 99790ccd966f5b20f3ee41ebf9fd86fe3e969a17
https://github.com/tribe29/checkmk/commit/99790ccd966f5b20f3ee41ebf9fd86fe3…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2019-09-23 (Mon, 23 Sep 2019)
Changed paths:
A .werks/10171
M cmk_base/automations/check_mk.py
Log Message:
-----------
10171 FIX Discovery: Fix triggering of discovery service after changing services
When editing services on the service discovery page it is intended that the
"Check_MK Discovery" service of the current host is retriggered to immediately
reflect the changes that have just been made to the service config.
This trigger was working as expected in previous 1.6.0 releases.
Change-Id: I5d2c5d3aba63eddb8e3501c3fc803eb6742f42ac
Commit: 89f974ba40896de59ba3fff58f031d730edf195f
https://github.com/tribe29/checkmk/commit/89f974ba40896de59ba3fff58f031d730…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2019-09-23 (Mon, 23 Sep 2019)
Changed paths:
A .werks/10172
Log Message:
-----------
10172 FIX Discovery service is now correctly operating on the WATO config instead of
core config
The Check_MK Discovery service needs to work with the WATO configuration world
instead of the "activated config" world. For example, if you edit the services
on the WATO service discovery page, you want the discovery service to be
updated right after editing the services in WATO.
Change-Id: I735557bfa21990976c03019c9895da37e4d54391
Compare:
https://github.com/tribe29/checkmk/compare/3a04735eca01...89f974ba4089