From 3828d309c601a553eabe5bf2438ea5532c97671e Mon Sep 17 00:00:00 2001 From: Lukas Lengler Date: Thu, 29 Aug 2024 09:11:56 +0200 Subject: [PATCH] Fix URLs still pointing to mathias-kettner.de documentation all URLs are now pointing to the Checkmk documentation (docs.checkmk.com) --- ChangeLog | 2 ++ docs/de_DE/about.html | 2 +- docs/de_DE/system_requirements.html | 2 +- docs/en_US/about.html | 26 +++++++++---------- docs/en_US/backend_mkbi.html | 2 +- docs/en_US/backend_mklivestatus.html | 2 +- docs/en_US/system_requirements.html | 2 +- .../classes/GlobalBackendmklivestatus.php | 4 +-- 8 files changed, 22 insertions(+), 20 deletions(-) diff --git a/ChangeLog b/ChangeLog index f08693511..290b2c624 100644 --- 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 index 00cb22f9c..e43c9fc35 100644 --- a/docs/de_DE/about.html +++ b/docs/de_DE/about.html @@ -33,7 +33,7 @@

Wie arbeitet NagVis?

NagVis ist ein Präsentationswerkzeug für die Informationen, die von Nagios gesammelt und mit Hilfe eines Backends zur Verfügung gestellt werden.

Die unterstützten Backends sind:

diff --git a/docs/de_DE/system_requirements.html b/docs/de_DE/system_requirements.html index 880eb3b90..53f6e6b5f 100644 --- a/docs/de_DE/system_requirements.html +++ b/docs/de_DE/system_requirements.html @@ -24,7 +24,7 @@

MKLivestatus (installiert, konfiguriert, lauffähig)

Seit NagVis 1.5 ist MKLivestatus das Default-Backend, weil es viel schneller, leichtgewichtiger und stabiler als NDO ist. Außerdem ist es einfacher zu handhaben und zu installieren. Sie benötigen keine Datenbank für MKLivestatus.

MKLivestatus ist ein Eventbroker-Modul für Nagios, das einen Unix-Socket versorgt, mit dem sich Addons wie NagVis verbinden können, um aktuelle Statusinformationen abzufragen.

-

MKLivestatus bekommen Sie auf der offiziellen MKLivestatus-Homepage. +

MKLivestatus bekommen Sie auf der offiziellen MKLivestatus-Homepage.

Webserver mit PHP-Unterstützung

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 index 1f1fb2ffb..5d09c4f6c 100644 --- a/docs/en_US/about.html +++ b/docs/en_US/about.html @@ -23,13 +23,13 @@

What is NagVis?

How does NagVis work?

In general NagVis is a presentation tool for the information which is gathered by Nagios and transferred using backends. -

The supported backends are:

- - The backend gets the information from the Nagios process (mklivestatus) or from a database (NDOUtils/IDOUtils, merlin). +

The supported backends are:

+ + The backend gets the information from the Nagios process (mklivestatus) or from a database (NDOUtils/IDOUtils, merlin).

You can place all objects from Nagios (Host, Services, Hostgroups, Servicegroups) on so called maps. Each map can be configured through its own configuration file. 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 @@

How does NagVis work?

for each object. Hover menus can easily be modified by changing the templates for them. You can also disable the hover menu.
By default the state of the objects is displayed using icons on the map. You can change these icons by adding iconsets from the NagVis homepage or create your own. The state of the objects can also be displayed as lines or as gadgets.

- -

Apart from the normal maps there is an automap. 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).
- To be able to use the automap you have to define the parents directives in your Nagios host objects.
- - Starting with NagVis 1.5 you can define more than one automap.

- + +

Apart from the normal maps there is an automap. 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).
+ To be able to use the automap you have to define the parents directives in your Nagios host objects.
+ + Starting with NagVis 1.5 you can define more than one automap.

+

Licensing

NagVis is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License version 2 as published by the Free Software Foundation.

diff --git a/docs/en_US/backend_mkbi.html b/docs/en_US/backend_mkbi.html index 6b17fa55c..7ad7633b0 100644 --- a/docs/en_US/backend_mkbi.html +++ b/docs/en_US/backend_mkbi.html @@ -7,7 +7,7 @@

Check_MK Business Intelligence Backend

The Check_MK Business Intelligence (BI) Backend is used to connect NagVis directly with the - aggregations configured within Check_MK BI.

+ aggregations configured within Check_MK BI.

The Check_MK BI API

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 index 144e8f5d8..51bdbd9d1 100644 --- a/docs/en_US/backend_mklivestatus.html +++ b/docs/en_US/backend_mklivestatus.html @@ -13,7 +13,7 @@

MKLivestatus backend

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 official documentation.

+ access provider take a look at the official documentation.

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 index 83e8b47e3..69340de33 100644 --- a/docs/en_US/system_requirements.html +++ b/docs/en_US/system_requirements.html @@ -19,7 +19,7 @@

MKLivestatus (installed, added to Nagios)

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.

-

You can get MKLivestatus from the official MKLivestatus Homepage.

+

You can get MKLivestatus from the official MKLivestatus Homepage.

Webserver with PHP support

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 Apache Webserver with mod_php.

diff --git a/share/server/core/classes/GlobalBackendmklivestatus.php b/share/server/core/classes/GlobalBackendmklivestatus.php index f5cf22c92..94c84fe68 100644 --- 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 * * 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 = '';