Icinga Web 2 - Einbinden von NagVis zur graphischen Visualisierung - Installation und Konfiguration unter CentOS 7.x
Mit NagVis steht ein sehr mächtiges Werkzeug zur Verfügung, wenn es darum geht IT-Landschaften in Übersichtsgraphiken mit Echtzeitdaten zur Verfügung zu stellen.
Aber werfen für die genauere Beschreibung einfach einen Blick in die sehr gute deutsche NagVis-Dokumentation.
… NagVis kann benutzt werden, um Nagios-Daten zu visualisieren, d.h. IT-Prozesse wie ein Mail-System oder eine Netzwerkinfrastruktur darzustellen. Durch die Benutzung von Daten, die von einem Backend zur Verfügung gestellt werden, kann NagVis die Objekte auf den Maps in regelmäßigen Intervallen aktualisieren. Diese Maps ermöglichen es, die Objekte auf verschiedene Arten zu arrangieren:
- physikalisch (z.B. alle Hosts in einem Rack/Raum/Bereich)
- logisch (z.B. alle Applikations-Server)
- geographisch (z.B. alle Hosts in einem Land)
- Geschäftsprozesse (z.B. alle Hosts/Services, die in einen Prozess involviert sind)
…
Installations-/Konfigurationsvorbereitungen
Vor der Installation und Konfiguration von NagVis und Icinga Web 2 bereiten wir unseren Icinga2-Monitoring-Server vor. Als erstes installieren wir noch benötigte RPM-Pakete, die zur Installation und Betrieb von NagVis benötigt werden.
# yum install rsync php-mbstring graphviz graphviz-php graphviz-gd
Damit später NagVis aktuelle Daten von unserem Icinga 2-Daemon anzeigen kann, muss NagVis auf aktuelle Daten von Icinga 2 zugreifen können. Hierzu nutzen wir das Icinga2-Feature livestatus. Mit dem folgenden Befehlsaufruf können wir überprüfen, ob die Funktion bereits aktiviert wurde.
# icinga2 feature list
Disabled features: compatlog debuglog gelf icingastatus opentsdb perfdata statusdata syslog Enabled features: api checker command graphite ido-mysql livestatus mainlog notification
Ist die Funktion livestatus noch nicht aktiviert, holen wir dies noch nach.
# icinga2 feature enable livestatus
Enabling feature livestatus. Make sure to restart Icinga 2 for these changes to take effect.
Zur Aktivierung führen wir nun noch einen Restart des Icinga 2 Daemon durch.
# systemctl restart icinga2
NagVis
Installation
Im nächsten Schritt werden wir NagVis installieren. Haben wir schon eine bestehende NagVis-Installation können wir den Schritt überspringen und gleich mit der Konfiguration von NagVis beginnen.
Als erstes holen wir uns das aktuelle tar.gz-Paket von der Nagvis-Homepage auf unseren Monitoring-Server.
# wget http://www.nagvis.org/share/nagvis-1.8.2.tar.gz
Anschließend entpacken wir das Archiv zur weiteren Installation.
# tar -zxf nagvis-1.8.2.tar.gz -C /usr/local/src
Im erstellten Verzeichnis finden wir eine Datei mit weiteren Installations-Informationen.
# less /usr/local/src/nagvis-1.8.2/INSTALL
============================================================================== NagVis 1.8 Quick Installation Instructions ============================================================================== Author: Andreas Husch, Lars Michelsen Document Version: 0.8 Date: 2013-07-20 Applies to: NagVis 1.4 - 1.8 ============================================================================== 1. Download NagVis -------------------- Get NagVis. The latest release can be found at www.nagvis.org. 2. Unpack NagVis -------------------- Unpack the archive to a temporary place (for example /tmp). And change to that directory > tar xvzf nagvis-1.*.tar.gz /tmp > cd /tmp/nagvis-1.* 3. Make installer executable -------------------- The installer is located in the root directory of the NagVis package. The installer has to be made executable before you can use it. > chmod +x install.sh 4. Run installer -------------------- Now you can run the installer. > ./install.sh Following the instructions of the installer should lead you to a working installation of NagVis. If you experience any problems please let us know. 5. Cleanup -------------------- You can remove the sources after installation. > rm -rf /tmp/nagvis-1.* 6. Additional information -------------------- 6.1 Command line parameters ------------------ For details about the command line parameters call the installer with the "-h" option. ============================================================================== Have fun using NagVis and please report bugs! ==============================================================================
Bei der Installation von NagVis greifen wir auf das Installationsscript install.sh aus dem NagVis-Paket zurück. Für unsere Monitoring-Umgebung nutzen wir nachfolgende Optionen, die dann später noch jeweils einzeln bestätigt bzw. verändert werden können. Erst einmal wechseln wir in das Installationsverzeichniss /usr/local/src/nagvis-1.8.2/.
# cd /usr/local/src/nagvis-1.8.2/
Anschließend starten wir das installationsscript.
# ./install.sh -n /usr/share/icinga2 -p /usr/share/nagvis -l "unix:/var/run/icinga2/cmd/livestatus" -b mklivestatus -u apache -g apache -w /etc/httpd/conf.d -a n
Der Hinweis, dass der Installer für Debain, Ubuntu und SuSE getestet sei, braucht uns nicht zu beunruhigen, dass das Script auch Ohne Probleme unter CentOS 7 läuft!
Bei der Frage zum Backend, bestätigen wir die Vorauswahl mklivestatus.
+------------------------------------------------------------------------------+
| Welcome to NagVis Installer 1.8.2 |
+------------------------------------------------------------------------------+
| This script is built to facilitate the NagVis installation and update |
| procedure for you. The installer has been tested on the following systems: |
| - Debian, since Etch (4.0) |
| - Ubuntu, since Hardy (8.04) |
| - SuSE Linux Enterprise Server 10 and 11 |
| |
| Similar distributions to the ones mentioned above should work as well. |
| That (hopefully) includes RedHat, Fedora, CentOS, OpenSuSE |
| |
| If you experience any problems using these or other distributions, please |
| report that to the NagVis team. |
+------------------------------------------------------------------------------+
| Do you want to proceed? [y]: y
+------------------------------------------------------------------------------+
| Starting installation of NagVis 1.8.2 |
+------------------------------------------------------------------------------+
| |
+--- Checking for tools -------------------------------------------------------+
| Using packet manager /bin/rpm found |
| |
+--- Checking paths -----------------------------------------------------------+
| Please enter the path to the nagios base directory [/usr/share/icinga2]:
| nagios path /usr/share/icinga2 found |
| Please enter the path to NagVis base [/usr/share/nagvis]:
| |
+--- Checking prerequisites ---------------------------------------------------+
| PHP 5.4 found |
| PHP Module: gd php found |
| PHP Module: mbstring php found |
| PHP Module: gettext compiled_in found |
| PHP Module: session compiled_in found |
| PHP Module: xml php found |
| PHP Module: pdo php found |
| Apache mod_php found |
| Checking Backends. (Available: mklivestatus,ndo2db,ido2db) |
| Do you want to use backend mklivestatus? [y]: y
| Do you want to use backend ndo2db? [n]:
| Do you want to use backend ido2db? [n]:
| Livestatus Socket (/var/run/icinga2/cmd/livestatus) found |
| PHP Module: sockets compiled_in found |
| Graphviz 2.30 found |
| Graphviz Module dot 2.30.1 found |
| Graphviz Module neato 2.30.1 found |
| Graphviz Module twopi 2.30.1 found |
| Graphviz Module circo 2.30.1 found |
| Graphviz Module fdp 2.30.1 found |
| SQLite 3.7 found |
| |
+--- Trying to detect Apache settings -----------------------------------------+
| Please enter the web path to NagVis [/nagvis]:
| Please enter the name of the web-server user [apache]:
| Please enter the name of the web-server group [apache]:
| create Apache config file [n]: y
| |
+--- Checking for existing NagVis ---------------------------------------------+
| |
+------------------------------------------------------------------------------+
| Summary |
+------------------------------------------------------------------------------+
| NagVis home will be: /usr/share/nagvis |
| Owner of NagVis files will be: apache |
| Group of NagVis files will be: apache |
| Path to Apache config dir is: /etc/httpd/conf.d |
| Apache config will be created: yes |
| |
| Installation mode: install |
| |
| Do you really want to continue? [y]: y
+------------------------------------------------------------------------------+
| Starting installation |
+------------------------------------------------------------------------------+
| Creating directory /usr/share/nagvis... done |
| Creating directory /usr/share/nagvis/var... done |
| Creating directory /usr/share/nagvis/var/tmpl/cache... done |
| Creating directory /usr/share/nagvis/var/tmpl/compile... done |
| Creating directory /usr/share/nagvis/share/var... done |
| Copying files to /usr/share/nagvis... done |
| Creating directory /usr/share/nagvis/etc/profiles... done |
| Creating main configuration file... done |
| adding base="/usr/share/nagvis" done |
| Adding MKLivestatus Backend... done |
| Adding webserver group to file_group... done |
| *** /etc/httpd/conf.d/nagvis.conf will NOT be overwritten ! |
| *** creating /etc/httpd/conf.d/nagvis.conf.2015-04-20_22:39:08 instead (comm |
| Creating web configuration file... done |
| Setting permissions for web configuration file... done |
| |
| |
| |
+--- Setting permissions... ---------------------------------------------------+
| /usr/share/nagvis/etc/nagvis.ini.php-sample done |
| /usr/share/nagvis/etc done |
| /usr/share/nagvis/etc/maps done |
| /usr/share/nagvis/etc/maps/* done |
| /usr/share/nagvis/etc/geomap done |
| /usr/share/nagvis/etc/geomap/* done |
| /usr/share/nagvis/etc/profiles done |
| /usr/share/nagvis/share/userfiles/images/maps done |
| /usr/share/nagvis/share/userfiles/images/maps/* done |
| /usr/share/nagvis/share/userfiles/images/shapes done |
| /usr/share/nagvis/share/userfiles/images/shapes/* done |
| /usr/share/nagvis/var done |
| /usr/share/nagvis/var/* done |
| /usr/share/nagvis/var/tmpl done |
| /usr/share/nagvis/var/tmpl/cache done |
| /usr/share/nagvis/var/tmpl/compile done |
| /usr/share/nagvis/share/var done |
| |
+------------------------------------------------------------------------------+
| Installation complete |
| |
| You can safely remove this source directory. |
| |
| For later update/upgrade you may use this command to have a faster update: |
| ./install.sh -n /usr/share/icinga2 -p /usr/share/nagvis -l "unix:/var/run/icinga2/cmd/livestatus" -b mklivestatus -u apache -g apache -w /etc/httpd/conf.d -a y
| |
| What to do next? |
| - Read the documentation |
| - Maybe you want to edit the main configuration file? |
| Its location is: /usr/share/nagvis/etc/nagvis.ini.php |
| - Configure NagVis via browser |
| <http://localhost/nagvis/config.php> |
| - Initial admin credentials: |
| Username: admin |
| Password: admin |
+------------------------------------------------------------------------------+
Das Installationsverzeichnis wird nun nicht mehr benötigt und kann bei Bedarf gelöscht werden. Für spätere Updates von NagVis sichern wir den angebotenen Scriptaufruf.
./install.sh -n /usr/share/icinga2 -p /usr/share/nagvis -l "unix:/var/run/icinga2/cmd/livestatus" \
-b mklivestatus -u apache -g apache -w /etc/httpd/conf.d -a y
(Erst-)Konfiguration
Apache Webserver
Das Installationsscript von NagVis hat uns im Verzeichnis /etc/httpd/conf.d/ eine mustergültige Konfigurationsdatei nagvis.conf hinterlegt. Dort brauchen wir nur noch die Berechtigungen zum Zugriff zu definieren.
# vim /etc/httpd/conf.d/nagvis.conf
- /etc/httpd/conf.d/nagvis.conf
# NagVis Apache2 sample configuration file # # ############################################################################# Alias /nagvis "/usr/share/nagvis/share" <Directory "/usr/share/nagvis/share"> Options FollowSymLinks AllowOverride None # Django : 2015-04-20 # default: Order allow,deny # Allow from all Require IP 10.0 # To enable Nagios basic auth on NagVis use the following options # Just uncomment it. Maybe you need to adjust the path to the # Auth user file. # # If you use the NagVis internal auth mechanism based on the web # for you won't need this. # #AuthName "NagVis Access" #AuthType Basic #AuthUserFile /usr/share/icinga2/etc/htpasswd.users #Require valid-user # With installed and enabled mod_rewrite there are several redirections # available to fix deprecated and/or wrong urls. None of those rules is # mandatory to get NagVis working. <IfModule mod_rewrite.c> RewriteEngine On RewriteBase /nagvis # Use mod_rewrite for old url redirection even if there are php files which # redirect the queries itselfs. In some cases the mod_rewrite redirect # is better than the php redirect. # # Using the php redirect seems to be better in some cases where https/http servers # are mixed. For example in OMD setups where using apache own mode and https in the # frontend and http in the backend apache servers. # # Disabling this redirect by default in the hope that the php direct works better. #RewriteCond %{REQUEST_URI} ^/nagvis(/config\.php|/index\.php|/|)(\?.*|)$ #RewriteRule ^(.*)$ /nagvis/frontend/nagvis-js/%1%2 [R=301,L] # Redirect old regular map links RewriteCond %{REQUEST_URI} ^/nagvis/frontend/(wui|nagvis-js) RewriteCond %{QUERY_STRING} map=(.*) RewriteRule ^(.*)$ /nagvis/frontend/nagvis-js/index.php?mod=Map&act=view&show=%1 [R=301,L] # Without map= param RewriteCond %{REQUEST_URI} ^/nagvis/frontend(/wui)?/?(index.php)?$ RewriteRule ^(.*)$ /nagvis/frontend/nagvis-js/index.php [R=301,L] # Redirect old rotation calls RewriteCond %{REQUEST_URI} ^/nagvis/frontend/nagvis-js RewriteCond %{QUERY_STRING} !mod RewriteCond %{QUERY_STRING} rotation=(.*) RewriteRule ^(.*)$ /nagvis/frontend/nagvis-js/index.php?mod=Rotation&act=view&show=%1 [R=301,L] </IfModule> </Directory>
Bevor wir unsere Konfigurationsanpassung mit einem Reload des Apache-Daemon vornehmen, testen wir die angepasste Konfigurationsdatei nagvis.conf auf syntaktische Fehler.
# apachectl -t
Syntax OK
Da nichts beanstandet wurde, führen wir nun einen Reload des Apache-Webservers durch.
# systemctl reload httpd
NagVis
Bei der Installation von NagVis mit Hilfe des Installationsscriptes wurde im Verzeichnis /usr/share/nagvis/etc/ die Konfigurationsdatei nagvis.ini.php angelegt. Diese Datei passen wir nun unserer Umgebung an.
- Sprache:
Für die Festlegung der zur Verfügung stehenden Sprachen passen wir die Option language an.# vim /usr/share/nagvis/etc/nagvis.ini.php
... Select language (Available by default: en_US, de_DE, fr_FR, pt_BR) ;language="en_US" ; Django : 2015-04-20 ; default: unset language="de_DE" ...
- Verzeichnis-Pfade:
Entsprechend unserer Icinga Web 2 Konfiguration passen wir die Sektion [paths] an.# vim /usr/share/nagvis/etc/nagvis.ini.php
... ; Path definitions [paths] ; absolute physical NagVis path ;base="/usr/local/nagvis/" base="/usr/share/nagvis/" ; absolute html NagVis path ;htmlbase="/nagvis" ; absolute html NagVis cgi path ;htmlcgi="/nagios/cgi-bin" ; Django : 2015-04-20 htmlcgi="/icingaweb2/monitoring" ...
- Links:
Das größte Augenmerk legen wir auf die Sektion [defaults]. Damit später beim Einbetten der NagVis-Seiten in Icinga Web 2 Verweise aus den NagVis-Graphiken nur als iframe von Icinga Web2 angezeigt werden, passen wir den Konfigurationsparameter urltarget an und setzen diesen auf den wert _parent.
Klicken wir später bei der Angzeige der NagVis Karten auf Hosts oder Services, wollen wir direkt zu den entsprechenden Icinga Web 2 Seiten gelangen. Hierzu passen wir die Parameter hosturl, hostgroupurl, serviceurl und servicegroupurl an.# vim /usr/share/nagvis/etc/nagvis.ini.php
... ; Django : 2015-04-20 ; don't show iframe in iframe urltarget="_parent" ; URL template for host object links ;hosturl="[htmlcgi]/status.cgi?host=[host_name]" ; Django : 2015-04-20 hosturl="[htmlcgi]/host/show?host=[host_name]" ; URL template for hostgroup object links ;hostgroupurl="[htmlcgi]/status.cgi?hostgroup=[hostgroup_name]" ; Django : 2015-04-20 hostgroupurl="[htmlcgi]/list/hosts?hostgroup=[hostgroup_name]" ; URL template for service object links ;serviceurl="[htmlcgi]/extinfo.cgi?type=2&host=[host_name]&service=[service_description]" ; Django : 2015-04-20 serviceurl="[htmlcgi]/service/show?host=[host_name]&service=[service_description]" ; URL template for servicegroup object links ;servicegroupurl="[htmlcgi]/status.cgi?servicegroup=[servicegroup_name]&style=detail" ; Django : 2015-04-20 servicegroupurl="[htmlcgi]/list/services?servicegroup=[servicegroup_name]" ...
- Automap:
Für das automatische Erstellen von Karten werden wir unter anderem später die Automap-Funktion verwenden. # vim /usr/share/nagvis/etc/nagvis.ini.php</code>... ; Options for the Automap [automap] ; Default URL parameters for links to the automap ;defaultparams="&childLayers=2" ; Default root host (NagVis uses this if it can't detect it via backend) ; You can configure a hostname here or use "<<<monitoring>>>" as "virtual" ; node which shows the parent tree and all hosts which have no parents ; defined below the is node. ;defaultroot="<<<monitoring>>>" ; Path to the graphviz binaries (dot,neato,...); Only needed if not in ENV PATH ;graphvizpath="/usr/bin/" ; Django : 2015-04-20 defaultparams="&childLayers=2" defaultroot="vml000117.dmz.nausch.org" graphvizpath="/usr/bin/" ...
Somit ergibt sich folgende NagVis-Konfigurations-Optionen:
# egrep -v '(^\s+;|^;|^$)' /usr/share/nagvis/etc/nagvis.ini.php
[global] file_group="apache" language="de_DE" [paths] base="/usr/share/nagvis/" htmlcgi="/icingaweb2/monitoring" [defaults] urltarget="_parent" hosturl="[htmlcgi]/host/show?host=[host_name]" hostgroupurl="[htmlcgi]/list/hosts?hostgroup=[hostgroup_name]" serviceurl="[htmlcgi]/service/show?host=[host_name]&service=[service_description]" servicegroupurl="[htmlcgi]/list/services?servicegroup=[servicegroup_name]" backend="live_1" [index] [automap] defaultparams="&childLayers=2" defaultroot="vml000117.dmz.nausch.org" graphvizpath="/usr/bin/" [wui] [worker] [backend_live_1] backendtype="mklivestatus" socket="unix:/var/run/icinga2/cmd/livestatus" [backend_ndomy_1] backendtype="ndomy" [rotation_demo] maps="demo-germany,demo-ham-racks,demo-load,demo-muc-srv1,demo-geomap,demo-automap" interval=15 [states]
Hier finden wir nochmals die komplette Konfigurationsdatei:
# vim /usr/share/nagvis/etc/nagvis.ini.php
; <?php return 1; ?>
; the line above is to prevent
; viewing this file from web.
; DON'T REMOVE IT!
; ----------------------------
; Default NagVis Configuration File
; At delivery everything here is commented out. The default values are set in the NagVis code.
; You can make your changes here, they'll overwrite the default settings.
; ----------------------------
; ----------------------------
; !!! The sections/variables with a leading ";" won't be recognised by NagVis (commented out) !!!
; ----------------------------
; General options which affect the whole NagVis installation
[global]
; Enable/Disable logging of security related user actions in Nagvis. For
; example user logins and logouts are logged in var/nagvis-audit.log
;audit_log="0"
;
; Defines the authentication module to use. By default NagVis uses the built-in
; SQLite authentication module. On delivery there is no other authentication
; module available. It is possible to add own authentication modules for
; supporting other authorisation mechanisms. For details take a look at the
; documentation.
;authmodule="CoreAuthModSQLite"
;
; Defines the authorisation module to use. By default NagVis uses the built-in
; SQLite authorisation module. On delivery there are some other modules available:
;
; - CoreAuthorisationModMySQL: Uses the same data structure as the SQLite authorisation
; module, but stores the data in a MySQL database.
; - CoreAuthorisationModMultisite: Uses information exported by Check_MKs Multisite
; to gather user permissions. This makes use of the roles defined for a user within
; multisite and the resulting permissions.
; - CoreAuthorisationModGroups: Assumes all users which should access NagVis are
; available in your monitoring core as contacts and assigned to contactgroups. Those
; contact group memberships are matched against a mapping table, which is defined in
; nagvis/etc/perms.db. This mapping table defines the permissions of each contact
; group within NagVis. Take a look at the docs for details.
;
; It is possible to add own authorisation modules for supporting other authorisation
; mechanisms. For details take a look at the documentation.
;authorisationmodule="CoreAuthorisationModSQLite"
;
; If you use CoreAuthorisationModGroups above, you might need these options:
; This option defines the path to your group permission mapping table. This file
; is searched within the NagVis etc directory.
;authorisation_group_perms_file="/usr/local/nagvis/etc/perms.db"
; This option is used to configure one or several backend_ids, seperated by ",", which
; should be used to get the users contact group memberships from.
;authorisation_group_backends="live_1"
;
; Sets the size of the controls in unlocked (edit) mode of the frontend. This
; defaults to a value of 10 which makes each control be sized to 10px * 10px.
;controls_size=10
;
; Dateformat of the time/dates shown in nagvis (For valid format see PHP docs)
;dateformat="Y-m-d H:i:s"
;
; Used to configure the preselected options in the "acknowledge problem" dialog
; dialog_ack_sticky=1
; dialog_ack_notify=1
; dialog_ack_persist=0
;
; File group and mode are applied to all files which are written by NagVis.
; Usualy these values can be left as they are. In some rare cases you might
; want to change these values to make the files writeable/readable by some other
; users in a group.
file_group="apache"
;file_mode="660"
;
; The server to use as source for the NagVis geomaps. Must implement the API which
; can be found on http://pafciu17.dev.openstreetmap.org/
;geomap_server="http://geomap.nagvis.org/"
;
; In some cases NagVis needs to open connections to the internet. The cases are:
; - The new geomap needs access to openstreetmap webservices to be able to fetch
; mapping information
; Most company networks don't allow direct HTTP access to the internet. The most
; networks require the users to use proxy servers for outbound HTTP requests.
; The proxy url to be used in NagVis can be configured here. One possible value
; is "tcp://127.0.0.1:8080".
;http_proxy=""
; Most proxies require authentication to access the internet. Use the format
; "<username>:<password>" to provide auth credentials
;http_proxy_auth=""
; Set the timeout (in seconds) for outbound HTTP requests (for example geomap requests)
;http_timeout=2
;
; Defines which translations of NagVis are available to the users
;language_available="de_DE,en_US,es_ES,fr_FR,pt_BR"
; Language detection steps to use. Available:
; - User: The user selection
; - Session: Language saved in the session (Usually set after first setting an
; explicit language)
; - Browser: Detection by user agent information from the browser
; - Config: Use configured default language (See below)
;language_detection="user,session,browser,config"
;
; Select language (Available by default: en_US, de_DE, fr_FR, pt_BR)
;language="en_US"
; Django : 2015-04-20
; default: unset
language="de_DE"
;
; Defines the logon module to use. There are three logon modules to be used by
; default. It is possible to add own logon modules for serving other dialogs or
; ways of logging in. For details take a look at the documentation.
;
; The delivered modules are:
;
; LogonMixed: The mixed logon module uses the LogonEnv module as default and
; the LogonDialog module as fallback when LogonEnv returns no username. This
; should fit the requirements of most environments.
;
; LogonDialog: This is an HTML logon dialog for requesting authentication
; information from the user.
;
; LogonEnv: It is possible to realise a fully "trusted" authentication
; mechanism like all previous NagVis versions used it before. This way the user
; is not really authenticated with NagVis. NagVis trusts the provided username
; implicitly. NagVis uses the configured environment variable to identify the
; user. You can add several authentication mechanisms to your webserver,
; starting from the basic authentication used by Nagios (.htaccess) to single
; sign-on environments.
; Simply set logonmodule to "LogonEnv", put the environment variable to use as
; username to the option logonenvvar and tell the authentication module to
; create users in the database when provided users does not exist. The option
; logonenvcreaterole tells the module to assign the new user to a specific role
; set to empty string to disable that behaviour.
;
; LogonMultisite: This module uses the authentication provided by auth_* cookies
; which have been generated by Check_MK multisite when using the cookie based
; authentication. Since 1.2.1i2 Check_MK uses a new cookie format. To be able
; to use this, you need to define a new option called logon_multisite_serials
; which points to the auth.serial file generated by Check_MK.
; Special options for this module:
;
; logon_multisite_htpasswd="/path/to/htpasswd"
; logon_multisite_serials="/path/to/auth.serials"
; logon_multisite_secret="/path/to/auth.secret"
; logon_multisite_createuser="1"
; logon_multisite_createrole="Guests"
;
;logonmodule="LogonMixed"
;logonenvvar="REMOTE_USER"
;logonenvcreateuser="1"
;logonenvcreaterole="Guests"
;
; Default rotation time of pages in rotations
;refreshtime=60
;
; Some user information is stored in sessions which are identified by session
; cookies placed on the users computer. The options below set the properties
; of the session cookie.
; Domain to set the cookie for. By default NagVis tries to auto-detect this
; options value by using the webserver's environment variables.
;sesscookiedomain="auto-detect"
; Absolute web path to set the cookie for. This defaults to configured
; paths/htmlbase option
;sesscookiepath="/nagvis"
; Lifetime of the NagVis session cookie in seconds. The default value is set to
; 24 hours. The NagVis session cookie contents will be renewed on every page
; visit. If a session is idle for more time than configured here it will become
; invalid.
;sesscookieduration="86400"
; Most modern browsers will deny javascript access to cookies if the HttpOnly
; flag is set. This prevents XSS attacks from stealing cookies. Default is off
; to not break any existing installations that rely on this functionality. Set
; to 1 to enable.
;sesscookiehttponly=0
; Most modern browsers will prevent cookies from being sent unencrypted if the
; Secure flag is set. Default is off since not all Nagvis installations require
; HTTPS. Set to 1 to enable.
;sesscookiesecure=0
;
; Staleness threshold (Only used with livestatus backend). Take a look at the
; Check_MK documentation for details about the staleness of hosts/services.
; The staleness means that an object has not received any state information for
; a given time. The configured value is a factor of the regular check interval.
; A value of 1.5 means that an object is marked as stale after one and a half
; check intervals have passed without update.
;staleness_threshold=1.5
;
; Start page to redirect the user to when first visiting NagVis without
; special parameters.
;startmodule="Overview"
;startaction="view"
; The startshow parameter is only used by some views at the moment. It is used
; by the Map module.
;startshow=""
;
; Turn on to enable some shinken related features in NagVis, like the
; min_business_impact-filter on automaps which can be used to render automaps
; based on the shinken attribute "business_impact".
;shinken_features=0
; Path definitions
[paths]
; absolute physical NagVis path
;base="/usr/local/nagvis/"
base="/usr/share/nagvis/"
; absolute html NagVis path
;htmlbase="/nagvis"
; absolute html NagVis cgi path
;htmlcgi="/nagios/cgi-bin"
; Django : 2015-04-20
htmlcgi="/icingaweb2/monitoring"
; Default values which get inherited to the maps and its objects
[defaults]
; default backend (id of the default backend)
;backend="live_1"
; background color of maps
;backgroundcolor="#ffffff"
; Enable/Disable the context menu on map objects. With the context menu you are
; able to bind commands or links to your map objects
;contextmenu=1
; Choose the default context template
;contexttemplate="default"
; Raise frontend events for problematic objects also on page loading. Set to 1 to
; enable this feature
;event_on_load=0
; Repeat frontend events in the given interval. The interval is configured in seconds.
;event_repeat_interval=0
; The time in seconds to repeat alerts for a problematic ojects for as configured in
; event_repeat_interval. This value defaults to -1, this leads to repeated events
; till the problematic state has been fixed.
;event_repeat_duration=-1
; Enable/Disable changing background color on state changes (Configured color is
; shown when summary state is PENDING, OK or UP)
;eventbackground=0
; Enable/Disable highlighting of the state changing object by adding a flashing
; border
;eventhighlight=1
; The duration of the event highlight in milliseconds (10 seconds by default)
;eventhighlightduration=10000
; The interval of the event highlight in milliseconds (0.5 seconds by default)
;eventhighlightinterval=500
; Enable/Disable the eventlog in the new javascript frontend. The eventlog keeps
; track of important actions and information
;eventlog=0
; Loglevel of the eventlog (available: debug, info, warning, critical)
;eventloglevel="info"
; Number of events kept in the scrollback
;eventlogevents="24"
; Height of the eventlog when visible in px
;eventlogheight="75"
; Hide/Show the eventlog on page load
;eventloghidden="1"
; Enable/Disable scrolling to the icon which changed the state when the icon is
; out of the visible scope
;eventscroll=1
; Enable/Disable sound signals on state changes
;eventsound=1
; enable/disable header menu
;headermenu="1"
; header template
;headertemplate="default"
; Enable/Diable the fading effect of the submenus in the header menu
;headerfade=1
; Show states in the sidebar header menu (if supported by template)
;header_show_states=0
; enable/disable hover menu
;hovermenu=1
; hover template
;hovertemplate="default"
; hover menu open delay (seconds)
;hoverdelay=0
; show children in hover menus
;hoverchildsshow=1
; limit shown child objects to n
;hoverchildslimit="10"
; order method of children (desc: descending, asc: ascending)
;hoverchildsorder="asc"
; sort method of children (s: state, a: alphabetical)
;hoverchildssort="s"
; default icons
;icons="std_medium"
; recognize only hard states (not soft)
;onlyhardstates=0
; recognize service states in host/hostgroup objects
;recognizeservices=1
; show map in lists (dropdowns, index page, ...)
;showinlists=1
; show map in multisite snapin
;showinmultisite=1
; Name of the custom stylesheet to use on the maps (The file needs to be located
; in the share/nagvis/styles directory)
;stylesheet=""
; target for the icon links
;urltarget="_self"
; Django : 2015-04-20
; don't show iframe in iframe
urltarget="_parent"
; URL template for host object links
;hosturl="[htmlcgi]/status.cgi?host=[host_name]"
; Django : 2015-04-20
hosturl="[htmlcgi]/host/show?host=[host_name]"
; URL template for hostgroup object links
;hostgroupurl="[htmlcgi]/status.cgi?hostgroup=[hostgroup_name]"
; Django : 2015-04-20
hostgroupurl="[htmlcgi]/list/hosts?hostgroup=[hostgroup_name]"
; URL template for service object links
;serviceurl="[htmlcgi]/extinfo.cgi?type=2&host=[host_name]&service=[service_description]"
; Django : 2015-04-20
serviceurl="[htmlcgi]/service/show?host=[host_name]&service=[service_description]"
; URL template for servicegroup object links
;servicegroupurl="[htmlcgi]/status.cgi?servicegroup=[servicegroup_name]&style=detail"
; Django : 2015-04-20
servicegroupurl="[htmlcgi]/list/services?servicegroup=[servicegroup_name]"
; URL template for dynamic group object links (disabled by default)
;dyngroupurl=""
; URL template for aggregations object links (disabled by default)
;aggrurl=""
; URL template for nested map links
;mapurl="[htmlbase]/index.php?mod=Map&act=view&show=[map_name]"
; Templates to be used for the different views.
;view_template="default"
; Enable/disable object labels for all objects
;label_show=0
; Configure the colors used by weathermap lines
;line_weather_colors="10:#8c00ff,25:#2020ff,40:#00c0ff,55:#00f000,70:#f0f000,85:#ffc000,100:#ff0000"
; Show mouse controllable elements for zooming the maps at the upper left corner of the map
;zoombar=0
; Enables scaling of the objects (icons, texts, lines, ...) when zooming the map. This can be disabled
; to have the objects remain at the same size during zooming
;zoom_scale_objects=1
; Options to configure the Overview page of NagVis
backend="live_1"
[index]
; Color of the overview background
;backgroundcolor=#ffffff
; Set number of map cells per row
;cellsperrow=4
; enable/disable header menu
;headermenu="1"
; header template
;headertemplate="default"
; Enable/Disable map listing
;showmaps=1
; Enable/Disable rotation listing
;showrotations=1
; Enable/Disable map thumbnails
;showmapthumbs=0
; Options for the Automap
[automap]
; Default URL parameters for links to the automap
;defaultparams="&childLayers=2"
; Default root host (NagVis uses this if it can't detect it via backend)
; You can configure a hostname here or use "<<<monitoring>>>" as "virtual"
; node which shows the parent tree and all hosts which have no parents
; defined below the is node.
;defaultroot="<<<monitoring>>>"
; Path to the graphviz binaries (dot,neato,...); Only needed if not in ENV PATH
;graphvizpath="/usr/bin/"
; Django : 2015-04-20
defaultparams="&childLayers=2"
defaultroot="vml000117.dmz.nausch.org"
graphvizpath="/usr/bin/"
; Options for the WUI
[wui]
; map lock time (minutes). When a user edits a map other users trying to edit
; the map are warned about this fact.
;maplocktime=5
; Show/hide the grid
;grid_show=0
; The color of the grid lines
;grid_color="#D5DCEF"
; The space between the single grid lines in pixels
;grid_steps=32
; Options for the new Javascript worker
[worker]
; The interval in seconds in which the worker will check for objects which need
; to be updated
;interval=10
; The maximum number of parameters used in ajax http requests
; Some intrusion detection/prevention systems have a problem with
; too many parameters in the url. Give 0 for no limit.
;requestmaxparams=0
; The maximum length of http request urls during ajax http requests
; Some intrusion detection/prevention systems have a problem with
; queries being too long
;requestmaxlength=1900
; The retention time of the states in the frontend in seconds. The state
; information will be refreshed after this time
;updateobjectstates=30
; ----------------------------
; Backend definitions
; ----------------------------
; Example definition of a livestatus backend.
; In this case the backend_id is live_1
; The path /usr/local/nagios/var/rw has to exist
[backend_live_1]
backendtype="mklivestatus"
; The status host can be used to prevent annoying timeouts when a backend is not
; reachable. This is only useful in multi backend setups.
;
; It works as follows: The assumption is that there is a "local" backend which
; monitors the host of the "remote" backend. When the remote backend host is
; reported as UP the backend is queried as normal.
; When the remote backend host is reported as "DOWN" or "UNREACHABLE" NagVis won't
; try to connect to the backend anymore until the backend host gets available again.
;
; The statushost needs to be given in the following format:
; "<backend_id>:<hostname>" -> e.g. "live_2:nagios"
;statushost=""
socket="unix:/var/run/icinga2/cmd/livestatus"
; Example definition for a MySQL backend
; in this example the ID of the Backend is "ndomy_1" you can define another ID.
[backend_ndomy_1]
; type of backend - MUST be set
backendtype="ndomy"
; The status host can be used to prevent annoying timeouts when a backend is not
; reachable. This is only useful in multi backend setups.
;
; It works as follows: The assumption is that there is a "local" backend which
; monitors the host of the "remote" backend. When the remote backend host is
; reported as UP the backend is queried as normal.
; When the remote backend host is reported as "DOWN" or "UNREACHABLE" NagVis won't
; try to connect to the backend anymore until the backend host gets available again.
;
; The statushost needs to be given in the following format:
; "<backend_id>:<hostname>" -> e.g. "live_2:nagios"
;statushost=""
; hostname for NDO-db
;dbhost="localhost"
; portname for NDO-db
;dbport=3306
; database name for NDO-db
;dbname="nagios"
; username for NDO-db
;dbuser="root"
; password for NDO-db
;dbpass=""
; prefix for tables in NDO-db
;dbprefix="nagios_"
; instance name for tables in NDO-db
;dbinstancename="default"
; maximum delay of the NDO Database in seconds
;maxtimewithoutupdate=180
; path to the cgi-bin of this backend
;htmlcgi="/nagios/cgi-bin"
; ----------------------------
; Rotation pool definitions
; ----------------------------
; in this example the browser switches between the maps demo and demo2 every 15
; seconds, the rotation is enabled by url: index.php?rotation=demo
[rotation_demo]
; These steps are rotated. The single steps may have optional prefixes like "Demo2:"
; which are used as display text on the index pages rotation list.
; You may also add external URLs as steps. Simply enclose the url using []
; instead of the map name.
maps="demo-germany,demo-ham-racks,demo-load,demo-muc-srv1,demo-geomap,demo-automap"
; rotation interval (seconds)
interval=15
; ----------------------------
; Action definitions
; ----------------------------
; Since NagVis 1.7.6 it is possible to use so called actions to extend the
; default context menu. This enables users to connect directly to the monitored
; hosts from the NagVis context menu. Here you can configure those actions.
;
; It is possible to add such actions to the context menus of service and host
; objects. They are not added blindly to all objects of those types, you can
; use the attribute "condition" to configure which objects shal have the
; specific actions. By default we use Nagios custom macros of the host object
; to make the actions visible/invisible. This filtering mechanism is not limited
; to custom macros, you can also use regular host attributes which are available
; within NagVis.
; With the option "client_os" you can configure the option to only be available
; on the clients which have a listed operating system running.
; Adds the action "connect via rdp" to service/host objects where the host object
; has the string "win" in the TAGS Nagios custom macro.
; When clicking on the link, NagVis generates a .rdp file which contains makes
; the client connect to the given host via RDP.
;[action_rdp]
;action_type="rdp"
;obj_type="host,service"
;condition="TAGS~win"
;client_os="win"
;domain=""
;username=""
; Adds the action "connect via ssh" to service/host objects which have the
; string "unix" in the TAGS Nagios custom macro. Is only added when NagVis
; detects that the client watching the map uses windows.
; When clicking on the link, NagVis generates a .cmd file which contains a
; call to putty which makes putty connect via SSH to this host.
;[action_win_ssh]
;action_type="win_ssh"
;obj_type="host,service"
;client_os="win"
;condition="TAGS~unix"
; Adds the action "connect via ssh" to service/host objects which have the
; string "unix" in the TAGS Nagios custom macro. Is only added when NagVis
; detects that the client watching the map uses linux or mac os.
; When clicking on the link, the browser opens the URL ssh://<address>/,
; you need to configure your clients browser to handle these urls correctly.
;[action_ssh_url]
;action_type="ssh_url"
;obj_type="host,service"
;client_os="mac,lnx"
;condition="TAGS~unix"
; Adds the action "connect via http" to service/host objects which have the
; string "web-80" in the TAGS Nagios custom macro
; When clicking on the link, the browser opens a new window with the URL
; http://<host_address>/. This can be changed by modyfing the context template.
;[action_http]
;action_type="http"
;obj_type="host,service"
;condition="TAGS~web-80"
; Adds the action "connect via http" to service/host objects which have the
; string "web-443" in the TAGS Nagios custom macro
; When clicking on the link, the browser opens a new window with the URL
; https://<host_address>/. This can be changed by modyfing the context template.
;[action_https]
;action_type="https"
;obj_type="host,service"
;condition="TAGS~web-443"
; ------------------------------------------------------------------------------
; Below you find some advanced stuff
; ------------------------------------------------------------------------------
; Configure different state related settings
[states]
; State coverage/weight: This defines the state handling behaviour. For example
; a critical state will cover a warning state and an acknowledged critical
; state will not cover a warning state.
;
; These options are being used when calculating the summary state of the map
; objects. The default values should fit most needs.
;
;down=10
;down_ack=6
;down_downtime=6
;unreachable=9
;unreachable_ack=6
;unreachable_downtime=6
;critical=8
;critical_ack=6
;critical_downtime=6
;warning=7
;warning_ack=5
;warning_downtime=5
;unknown=4
;unknown_ack=3
;unknown_downtime=3
;error=4
;error_ack=3
;error_downtime=3
;up=2
;ok=1
;unchecked=0
;pending=0
;
; Colors of the different states. The colors are used in lines and hover menus
; and for example in the frontend highlight and background event handler
;
;unreachable_bgcolor=#F1811B
;unreachable_color=#F1811B
;unreachable_ack_bgcolor=
;unreachable_downtime_bgcolor=
;down_bgcolor=#FF0000
;down_color=#FF0000
;down_ack_bgcolor=
;down_downtime_bgcolor=
;critical_bgcolor=#FF0000
;critical_color=#FF0000
;critical_ack_bgcolor=
;critical_downtime_bgcolor=
;warning_bgcolor=#FFFF00
;warning_color=#FFFF00
;warning_ack_bgcolor=
;warning_downtime_bgcolor=
;unknown_bgcolor=#FFCC66
;unknown_color=#FFCC66
;unknown_ack_bgcolor=
;unknown_downtime_bgcolor=
;error_bgcolor=#0000FF
;error_color=#0000FF
;up_bgcolor=#00FF00
;up_color=#00FF00
;ok_bgcolor=#00FF00
;ok_color=#00FF00
;unchecked_bgcolor=#C0C0C0
;unchecked_color=#C0C0C0
;pending_bgcolor=#C0C0C0
;pending_color=#C0C0C0
;
; Sound of the different states to be used by the sound eventhandler in the
; frontend. The sounds are only being fired when changing to some
; worse state.
;
;unreachable_sound=std_unreachable.mp3
;down_sound=std_down.mp3
;critical_sound=std_critical.mp3
;warning_sound=std_warning.mp3
;unknown_sound=
;error_sound=
;up_sound=
;ok_sound=
;unchecked_sound=
;pending_sound=
; -------------------------
; EOF
; -------------------------
Icinga Web 2 Modul
Installation
Für das Einbetten der NagVis-Karten in Icinga Web2 greifen wir auf das Modul icingaweb2-module-nagvis zurück.
Als erstes holen wir uns das Modul von der GitHub Seite.
# wget https://github.com/divetoh/icingaweb2-module-nagvis/archive/master.zip
Dann entpacken wir das ZIP-Archiv.
# unzip master.zip -d /usr/local/src/
Abschließend verschieben wir das Unterverzeichnis nagvis in das Icinga Web 2 Modulverzeichnis.
# mv /usr/local/src/icingaweb2-module-nagvis-master/nagvis/ /usr/share/icingaweb2/modules/
Konfiguration
Zur Konfiguration von Icinga Web 2 öffnen wir die URL unserer Icinga-Installation.
$ firefox https://orwell.nausch.org/icingaweb2/
Hier melden wir uns nun wie gewohnt an.
Auf der linken Seite klicken wir auf den Menüpunkt System.
Hier licken wir nun auf den Menüpunkt Module.
In diesem Fenster wählen wir dann unser neues Modul nagvis an.
Zum aktivieren klicken wir auf der rechten Bildschirmseite auf den Schriftzug enable.
Zur abschließenden Modulkonfiguration klicken wir nun rechts oben auf den Reiter Nagvis.
Hier tragen wir nun die URL bzw. das Verzeichnis unserer NagVis-Installation ein und klicken abschließend auf die Schaltfläche Save Changes.
Start der NagVis-Anwendung
Da wir die initiale Konfiguration abgeschlossen haben, können wir nun Das Modul NagVis aufrufen. Hierzu klicken wir im Menü links auf den Menüpunkt Nagvis.
Zur Erstanmeldung am Modul Nagvis geben wir als Anmeldedaten jeweils admin ein und klicken dann auf die Schaltfläche Einloggen.
Einen ersten Eindruck können wir uns mit Hilfe der bei der Erstinstallation angelegten Demo-Karten verschaffen.
individuelle Konfiguration
User
Bei der Installation von NagVis mit Hilfe des Installationsscriptes werden neben dem Admin-User noch ein Gast-Zugang angelegt. Hier legen wir nun für unsere(n) Icinga 2 Admin(s) jeweils einen User an. Dazu tragen wir Nutzernamen und Passwort in die zugehörigen Felder ein und klicken dann auf die Schaltfläche Nutzer erstellen.
Anschließend weißen wir dem zuständigen Administrator die Anmin-Rechte an NagVis zu. Nach Auswahl des Benutzerkontos und Zuweisung der Rechte klicken wir auf die Schaltfläche Nutzer bearbeiten.
Den ungenutzten Gastzugang löschen wir nun noch, indem wir den Nutzernamen beim Menüpunkt Nutzer löschen auswählen und die Schaltfläche Nutzer löschen anklicken.
Zu guter Letzt ändern wir das Standardpasswort des Accounts admin noch ab. Dazu wählen wir aus dem Nutzermenü rechts oben den Menüpunkt Passwort ändern aus.
Nach Eingabe des alten Passwortes admin tragen wir 2x unser neues Passwort ein und klicken dann auf die Schaltfläche Passwort ändern.
Demokartenmaterial
Die mitgelieferten Karten dienen unter anderem dazu, sich über die Möglichkeiten von NagVis zu informieren bzw. dienen als Vorlagen für eigene Karten. Wir löschen daher die Kartendefinitionen nicht, sonder verschieben nur die zugehörigen Dateien in ein backup-Verzeichnis.
Als erstes legen wir uns das Backup-Verzeichnis an.
# mkdir /root/nagvis
Dann verschieben wir die map-Konfigurationsdateien in dieses Verzeichnis.
# mv /usr/share/nagvis/etc/maps/* /root/nagvis/
Abschließend deaktivieren wir noch die Parameter des Definitionsbereichs Rotation pool definitions in der Datei
# vim /usr/share/nagvis/etc/nagvis.ini.php
... ; ---------------------------- ; Rotation pool definitions ; ---------------------------- ; in this example the browser switches between the maps demo and demo2 every 15 ; seconds, the rotation is enabled by url: index.php?rotation=demo ; Django : 2015-04-20 ; default: [rotation_demo] ; These steps are rotated. The single steps may have optional prefixes like "Demo2:" ; which are used as display text on the index pages rotation list. ; You may also add external URLs as steps. Simply enclose the url using [] ; instead of the map name. ; Django : 2015-04-20 ; default: maps="demo-germany,demo-ham-racks,demo-load,demo-muc-srv1,demo-geomap,demo-automap" ; rotation interval (seconds) ; Django : 2015-04-20 ; default: interval=15 ...
Automap
Im folgendem Konfigurationsbeispiel, werden wir uns nun eine Automap für unseren Icinga 2 Host und den überwachten Hosts anlegen.
Als erstes wählen wir aus dem NagVis-Menü Optionen den Menüpunkt
Hier wählen wir dann die Standard-Datenquelle aus und klicken anschließend auf die Schaltfläche Speichern.
Nun definieren wir uns eine eigene Karte vom Typ automap; dafür wählen wir den Menüpunkt Karten verwalten aus dem Menü Optionen aus.
Zum Generieren der Automap befüllen wir beim Menüpunkt Karte erstellen die Felder ID (Interner Name) und Alias. Beim Kartentyp wählen wir Automap basierend auf Eltern/Kind Beziehungen aus. Abschließend klicken wir auf die Schaltfläche Erstellen und sichern damit unsere Eingaben.
Basieren auf den Monitoringkonfiguration unserer Icinga 2 Umgebung wird nach einer kurzen Zeit die generierte automap angezeigt.
Sobald wir mit der Maus übe einen der überwachten Host streichen, werden weitere Details des Hosts eingeblendet.
Klicken wir auf einen Host, gelangen wir direkt auf die Icinga Web 2 Detailseite des Hosts.
127.0.0.1