[checkmk-commits] [tribe29/checkmk] f8f3a6: 10510 Added more link views for Host Groups (Summary)

Branch: refs/heads/master Home: https://github.com/tribe29/checkmk Commit: f8f3a6d78228d89e8d07f09103ae13f75c9ce3ad https://github.com/tribe29/checkmk/commit/f8f3a6d78228d89e8d07f09103ae13f75… Author: Marcel Arentz &lt;marcel.arentz(a)tribe29.com&gt; Date: 2019-11-04 (Mon, 04 Nov 2019) Changed paths: A .werks/10510 M cmk/gui/plugins/views/builtin.py M tests/unit/cmk/gui/test_gui_config.py Log Message: ----------- 10510 Added more link views for Host Groups (Summary) The view Host Groups (Summary) did not have any links in the shown data, that would display more details. With this change, all statistics are now linked to such a more detailed view. Change-Id: Ibfea4ce953428edeafa83bcafcd68a86dd0f050d Commit: cb7d148c653b6e7bc2365ad7d842e9578e79fa02 https://github.com/tribe29/checkmk/commit/cb7d148c653b6e7bc2365ad7d842e9578… Author: Andreas Umbreit &lt;andreas.umbreit(a)tribe29.com&gt; Date: 2019-11-04 (Mon, 04 Nov 2019) Changed paths: A .werks/10428 Log Message: ----------- 10428 Distributed Agent Updates It is now possible to deploy baked agents via remote sites within a distributed monitoring configuration. Prerequisites for this feature are a monitoring setup using distributed WATO and the possibility to establish a connection from remote sites to the central site via HTTP/HTTPS. This feature is realized as follows: Update requests to the remote sites get forwarded to the central site – The entire configuration and the agent baking process is done on the central site. Agent packages that got requested once at a remote site will get cached (as long as they are valid) there to save unnecessary traffic. Additionally, the requested data will be checked for consistency on the remote site, again to save unnecessary traffic to the central site. In contrast to a single-site-setup, the update server for a host doesn't come exclusively from the agent updater ruleset, but gets transmitted to the host on it's registration and update requests. A host will receive the Checkmk site that it is monitored on as it's update server. Putting this together, an input of a Checkmk-server is only needed once on registration. If a connection to the automatic update server is failing, the previously saved server (from agent updater ruleset or from manual registration) will be contacted as a fallback. This feature also introduces a faciliated agent updater ruleset configuration - especially when it comes to HTTPS handling - and some additional global settings that have to be configured to enable the distributed agent updates. All new or adapted configuration values get migrated in a way that maintains the behavior of an existing agent updater ruleset. For details about configuration and how to enable (or disable) this new feature, please have a look at the <a href="https://checkmk.com/cms_agent_deployment.html"> Automatic Agent Updates</a> article at the official Checkmk guide. Change-Id: Ibc182a967cc98009efb0110e06be616d93899ae2 Compare: https://github.com/tribe29/checkmk/compare/c56d51b672d9...cb7d148c653b