From noreply@github.com Mon Nov 4 16:51:08 2019 From: Lars To: checkmk-commits@lists.checkmk.com Subject: [checkmk-commits] [tribe29/checkmk] f8f3a6: 10510 Added more link views for Host Groups (Summary) Date: Mon, 04 Nov 2019 07:51:05 -0800 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3969725090143387623==" --===============3969725090143387623== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Branch: refs/heads/master Home: https://github.com/tribe29/checkmk Commit: f8f3a6d78228d89e8d07f09103ae13f75c9ce3ad https://github.com/tribe29/checkmk/commit/f8f3a6d78228d89e8d07f09103ae1= 3f75c9ce3ad Author: Marcel Arentz 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/cb7d148c653b6e7bc2365ad7d842e= 9578e79fa02 Author: Andreas Umbreit 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 distribut= ed monitoring configuration. Prerequisites for this feature are a monitoring set= up using distributed WATO and the possibility to establish a connection from rem= ote 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 =E2=80=93 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 sa= ve unnecessary traffic. Additionally, the requested data will be checked for con= sistency 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 regi= stration 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 re= gistration. If a connection to the automatic update server is failing, the previously sav= ed 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 ha= ve 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 featu= re, please have a look at the = Automatic Agent Updates article at the official Checkmk guide. Change-Id: Ibc182a967cc98009efb0110e06be616d93899ae2 Compare: https://github.com/tribe29/checkmk/compare/c56d51b672d9...cb7d148c65= 3b --===============3969725090143387623==--