[checkmk-commits] [tribe29/checkmk] b877bd: 10374 NagVis: Updated to 1.9.16

Branch: refs/heads/1.6.0 Home: https://github.com/tribe29/checkmk Commit: b877bd508f7480fdb902e260b236422a27c6ae6a https://github.com/tribe29/checkmk/commit/b877bd508f7480fdb902e260b236422a2… Author: Lars Michelsen &lt;lm(a)tribe29.com&gt; Date: 2019-10-24 (Thu, 24 Oct 2019) Changed paths: A .werks/10374 R omd/packages/nagvis/nagvis-1.9.15.tar.gz A omd/packages/nagvis/nagvis-1.9.16.tar.gz M omd/packages/nagvis/nagvis.make Log Message: ----------- 10374 NagVis: Updated to 1.9.16 NagVis is now able to work with encrypted Livestatus configurations. Change-Id: Ib1ee6c41f962a2f0413f80b27b42180a606ec704 Commit: 9fec821e51ef0fde21fcccf0ba3d896f138aacd5 https://github.com/tribe29/checkmk/commit/9fec821e51ef0fde21fcccf0ba3d896f1… Author: Lars Michelsen &lt;lm(a)tribe29.com&gt; Date: 2019-10-24 (Thu, 24 Oct 2019) Changed paths: A .werks/10375 M cmk/gui/wato/pages/sites.py M cmk/gui/watolib/sites.py Log Message: ----------- 10375 FIX NagVis backends now work with encrypted Livestatus WATO automatically configures backends in NagVis on the central site of a distributed WATO setup. When the livestatus proxy was not used, the backends could not be configured to connect to encrypted Livestatus sites. This is now automatically done. These backends are stored in <tt>etc/nagvis/conf.d/cmk_backends.ini.php</tt>. In case the Livestatus Proxy Daemon is used, NagVis always uses the local unix socket connection to the Livestatus proxy. In case it is not used, NagVis will connect to either the plain text socket or the encrypted Livestatus socket, just like the Checkmk GUI. When verifying certificates NagVis uses the trusted certificate authorities of Checkmk. Change-Id: I408e62895e4c71779bd680a642baa4cdd9ff9de7 Compare: https://github.com/tribe29/checkmk/compare/03e848fe9f72...9fec821e51ef