Fix URLs still pointing to mathias-kettner.de documentation

all URLs are now pointing to the Checkmk documentation (docs.checkmk.com)
NagVis · Aug 29, 2024 · 3828d30 · 3828d30
1 parent 8b1f070
commit 3828d30
Show file tree

Hide file tree

Showing 8 changed files with 22 additions and 20 deletions.
diff --git a/ChangeLog b/ChangeLog
@@ -4,6 +4,8 @@ Core:
          Entering correct proxy URLS with ports and one of the following schemas
          (tcp, udp, unix, udg, ssl, tls) would cause an error (Invalid format given)
          even though these proxies are correct.
+  * FIX: URLs still pointing to mathias-kettner.de documentation are now pointing to
+         the Checkmk documentation (docs.checkmk.com).
 
 Security
   * Added cookie session timestamps validation when Nagvis is run within Checkmk

diff --git a/docs/de_DE/about.html b/docs/de_DE/about.html
@@ -33,7 +33,7 @@ <h2>Wie arbeitet NagVis?</h2>
         <p>NagVis ist ein Pr&auml;sentationswerkzeug f&uuml;r die Informationen, die von Nagios gesammelt und mit Hilfe eines Backends zur Verf&uuml;gung gestellt werden.
         <p>Die unterst&uuml;tzten Backends sind:</p>
         <ul>
-            <li><a href="http://mathias-kettner.de/checkmk_livestatus.html">mklivestatus</a> (Default seit NagVis 1.5)</li>
+            <li><a href="https://docs.checkmk.com/latest/en/livestatus.html">mklivestatus</a> (Default seit NagVis 1.5)</li>
             <li><a href="http://www.nagios.org/download/addons">NDOUtils</a> / <a href="http://docs.icinga.org/latest/en/ch12">IDOUtils</a> (erfordert MySQL)</li>
             <li><a href="https://github.com/ITRS-Group/monitor-merlin">merlin</a> (erfordert MySQL)</li>
         </ul>

diff --git a/docs/de_DE/system_requirements.html b/docs/de_DE/system_requirements.html
@@ -24,7 +24,7 @@ <h2>MKLivestatus (installiert, konfiguriert, lauff&auml;hig)</h2>
     <p>Seit NagVis 1.5 ist MKLivestatus das Default-Backend, weil es viel schneller, leichtgewichtiger und stabiler als NDO ist.
         Au&szlig;erdem ist es einfacher zu handhaben und zu installieren. Sie ben&ouml;tigen keine Datenbank f&uuml;r MKLivestatus.</p>
     <p>MKLivestatus ist ein Eventbroker-Modul f&uuml;r Nagios, das einen Unix-Socket versorgt, mit dem sich Addons wie NagVis verbinden k&ouml;nnen, um aktuelle Statusinformationen abzufragen.</p>
-    <p>MKLivestatus bekommen Sie auf der <a href=http://www.mathias-kettner.de/checkmk_livestatus.html>offiziellen MKLivestatus-Homepage</a>.
+    <p>MKLivestatus bekommen Sie auf der <a href=https://docs.checkmk.com/latest/en/livestatus.html>offiziellen MKLivestatus-Homepage</a>.
 
     <h2>Webserver mit PHP-Unterst&uuml;tzung</h2>
     NagVis ist eine webbasierte Applikation, die in JavaScript und PHP realisiert ist.

diff --git a/docs/en_US/about.html b/docs/en_US/about.html
@@ -23,13 +23,13 @@ <h2>What is NagVis?</h2>
     <a name="howworks"></a>
     <h2>How does NagVis work?</h2>
         <p>In general NagVis is a presentation tool for the information which is gathered by Nagios and transferred using backends. 
-        <p>The supported backends are:</p>
-        <ul>
-        <li><a href="http://mathias-kettner.de/checkmk_livestatus.html">mklivestatus</a> (default since NagVis 1.5)</li>
-        <li><a href="http://www.nagios.org/download/addons">NDOUtils</a> / <a href="http://docs.icinga.org/latest/en/ch12">IDOUtils</a> (requires MySQL)</li>
-        <li><a href="https://github.com/ITRS-Group/monitor-merlin">merlin</a> (requires MySQL)</li>
-        </ul>
-        The backend gets the information from the Nagios process (mklivestatus) or from a database (NDOUtils/IDOUtils, merlin).
+        <p>The supported backends are:</p>
+        <ul>
+        <li><a href="https://docs.checkmk.com/latest/en/livestatus.html">mklivestatus</a> (default since NagVis 1.5)</li>
+        <li><a href="http://www.nagios.org/download/addons">NDOUtils</a> / <a href="http://docs.icinga.org/latest/en/ch12">IDOUtils</a> (requires MySQL)</li>
+        <li><a href="https://github.com/ITRS-Group/monitor-merlin">merlin</a> (requires MySQL)</li>
+        </ul>
+        The backend gets the information from the Nagios process (mklivestatus) or from a database (NDOUtils/IDOUtils, merlin).
         <p>You can place all objects from Nagios (Host, Services, Hostgroups, Servicegroups) on so called maps. Each map can be configured through its own
         <a href="map_config_format_description.html">configuration file</a>. You can edit the configuration files directly by using your favourite text editor 
         or the web configuration mechanisms. Furthermore you can add some special NagVis objects to the maps. These objects are shapes, textboxes and 
@@ -40,12 +40,12 @@ <h2>How does NagVis work?</h2>
         for each object. Hover menus can easily be modified by changing the <a href="hover_templates.html">templates</a> for them. You can also disable the hover menu.<br> 
         By default the state of the objects is displayed using icons on the map. You can change these icons by adding <a href="extending/iconsets.html">iconsets</a> from the NagVis 
         homepage or create your own. The state of the objects can also be displayed as lines or as <a href="gadgets.html">gadgets</a>.</p>
-
-        <p>Apart from the normal maps there is an <a href="automap.html">automap</a>. The objects are places automatically starting from the root host you specified. Depending on the value of the directice "filter_by_state" it will show all objects or only the ones in a non-OK state (including the way from the root object).<br>
-        To be able to use the automap you have to define the parents directives in your Nagios host objects.<br>
-
-        Starting with NagVis 1.5 you can define more than one automap.</p>
-
+
+        <p>Apart from the normal maps there is an <a href="automap.html">automap</a>. The objects are places automatically starting from the root host you specified. Depending on the value of the directice "filter_by_state" it will show all objects or only the ones in a non-OK state (including the way from the root object).<br>
+        To be able to use the automap you have to define the parents directives in your Nagios host objects.<br>
+
+        Starting with NagVis 1.5 you can define more than one automap.</p>
+
     <a name="licensing"></a>
     <h2>Licensing</h2>
         <p>NagVis is free software; you can redistribute it and/or modify it under the terms of the <a href="http://www.gnu.org/licenses/old-licenses/gpl-2.0.html">GNU General Public License version 2</a> as published by the <a href="www.fsf.org">Free Software Foundation</a>.</p>

diff --git a/docs/en_US/backend_mkbi.html b/docs/en_US/backend_mkbi.html
@@ -7,7 +7,7 @@
  <body>
     <h1>Check_MK Business Intelligence Backend</h1>
     <p>The Check_MK Business Intelligence (BI) Backend is used to connect NagVis directly with the
-       aggregations configured within <a href="http://mathias-kettner.de/checkmk_bi.html" target="_blank">Check_MK BI</a>.</p>
+       aggregations configured within <a href="https://docs.checkmk.com/latest/en/bi.html" target="_blank">Check_MK BI</a>.</p>
 
     <h2>The Check_MK BI API</h2>
     <p>Check_MK BI offers a webservice which is called by HTTP GET requests and

diff --git a/docs/en_US/backend_mklivestatus.html b/docs/en_US/backend_mklivestatus.html
@@ -13,7 +13,7 @@ <h1>MKLivestatus backend</h1>
              than the NDO, Livestatus does not actively write out data e.g. to the disk.
              Instead, it opens a socket for external applications to connect to and fetches
              the current status information from Nagios. For details about the new data
-             access provider take a look at the <a href="http://www.mathias-kettner.de/checkmk_livestatus.html#H1:How to access Nagios status data" target="_blank">official documentation</a>.</p>
+             access provider take a look at the <a href="https://docs.checkmk.com/latest/en/livestatus.html" target="_blank">official documentation</a>.</p>
         <p>Since the first NagVis 1.5 release the mklivestatus backend is included on
              delivery. It performs much better than all other existing backends and
              comes with less overhead than other backends. No additional database is

diff --git a/docs/en_US/system_requirements.html b/docs/en_US/system_requirements.html
@@ -19,7 +19,7 @@ <h2>MKLivestatus (installed, added to Nagios)</h2>
         <p>MKLivestatus is an Event Broker Module for Nagios which serves a unix socket
             where third party addons like NagVis can connect to for gathering live status
             information in a very fast way.</p>
-        <p>You can get MKLivestatus from the <a href="http://www.mathias-kettner.de/checkmk_livestatus.html" target="_blank">official MKLivestatus Homepage</a>.</p>
+        <p>You can get MKLivestatus from the <a href="https://docs.checkmk.com/latest/en/livestatus.html" target="_blank">official MKLivestatus Homepage</a>.</p>
 
         <h2>Webserver with PHP support</h2>
         <p>NagVis is a web based application realised in Javascript and PHP. You need a webserver with PHP support to run NagVis. We recommend the usage of <a href="http://www.apache.org/" target="_blank">Apache Webserver</a> with <a href="http://www.apache.net/" target="_blank">mod_php</a>.</p>

diff --git a/share/server/core/classes/GlobalBackendmklivestatus.php b/share/server/core/classes/GlobalBackendmklivestatus.php
@@ -5,7 +5,7 @@
  *
  * Backend class for handling object and state information using the
  * livestatus NEB module. For mor information about CheckMK's Livestatus
- * Module please visit: http://mathias-kettner.de/checkmk_livestatus.html
+ * Module please visit: https://docs.checkmk.com/latest/en/livestatus.html
  *
  * Copyright (c) 2010 NagVis Project  (Contact: info@nagvis.org),
  *                    Mathias Kettner (Contact: mk@mathias-kettner.de)
@@ -32,7 +32,7 @@
  * @author  Lars Michelsen  <lm@larsmichelsen.com>
  *
  * For mor information about CheckMK's Livestatus Module
- * please visit: http://mathias-kettner.de/checkmk_livestatus.html
+ * please visit: https://docs.checkmk.com/latest/en/livestatus.html
  */
 class GlobalBackendmklivestatus implements GlobalBackendInterface {
     private $backendId = '';