Unterschiede
Hier werden die Unterschiede zwischen zwei Versionen angezeigt.
Beide Seiten der vorigen Revision Vorhergehende Überarbeitung Nächste Überarbeitung | Vorhergehende Überarbeitung | ||
centos:web_c7:icinga:nagvis [20.04.2015 20:54. ] – [Icinga Web 2 Modul] django | centos:web_c7:icinga:nagvis [22.07.2019 14:58. ] (aktuell) – Externe Bearbeitung 127.0.0.1 | ||
---|---|---|---|
Zeile 40: | Zeile 40: | ||
- | ===== Installation | + | ===== NagVis |
- | ==== 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. | + | 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 **[[centos: |
Als erstes holen wir uns das aktuelle **tar.gz**-Paket von der [[http:// | Als erstes holen wir uns das aktuelle **tar.gz**-Paket von der [[http:// | ||
Zeile 121: | Zeile 121: | ||
<WRAP center round tip 90%> | <WRAP center round tip 90%> | ||
- | Der Hinweis, dass der Installer für Debain, Ubuntu und SuSE getestet sei, braucht uns nicht zu beunruhigen, | + | Der Hinweis, dass der Installer für Debain, Ubuntu und SuSE getestet sei, braucht uns nicht zu beunruhigen, |
</ | </ | ||
Zeile 261: | Zeile 261: | ||
-b mklivestatus -u apache -g apache -w / | -b mklivestatus -u apache -g apache -w / | ||
+ | ==== (Erst-)Konfiguration ==== | ||
+ | === Apache Webserver === | ||
+ | Das Installationsscript von NagVis hat uns im Verzeichnis // | ||
+ | Dort brauchen wir nur noch die Berechtigungen zum Zugriff zu definieren. | ||
+ | # vim / | ||
+ | <file apache / | ||
+ | # | ||
+ | # ############################################################################# | ||
- | + | Alias /nagvis "/ | |
- | ==== Icinga Web 2 Modul ==== | + | |
- | FIXME | + | < |
+ | Options FollowSymLinks | ||
+ | AllowOverride None | ||
+ | # Django : 2015-04-20 | ||
+ | # default: Order allow, | ||
+ | # 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 " | ||
+ | #AuthType Basic | ||
+ | # | ||
+ | #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. | ||
+ | < | ||
+ | RewriteEngine On | ||
+ | RewriteBase /nagvis | ||
+ | |||
+ | # | ||
+ | # 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. | ||
+ | # | ||
+ | # | ||
+ | |||
+ | # Redirect old regular map links | ||
+ | RewriteCond %{REQUEST_URI} ^/ | ||
+ | RewriteCond %{QUERY_STRING} map=(.*) | ||
+ | RewriteRule ^(.*)$ /nagvis/frontend/ | ||
+ | |||
+ | # Without map= param | ||
+ | RewriteCond %{REQUEST_URI} ^/ | ||
+ | RewriteRule ^(.*)$ / | ||
- | # unzip master.zip -d /usr/share/icingaweb2/modules | + | |
+ | RewriteCond %{REQUEST_URI} ^/ | ||
+ | RewriteCond %{QUERY_STRING} !mod | ||
+ | RewriteCond %{QUERY_STRING} rotation=(.*) | ||
+ | RewriteRule ^(.*)$ / | ||
+ | </IfModule> | ||
+ | </Directory> | ||
+ | </file> | ||
- | # mv / | + | Bevor wir unsere Konfigurationsanpassung mit einem Reload des Apache-Daemon vornehmen, testen wir die angepasste Konfigurationsdatei **nagvis.conf** auf syntaktische Fehler. |
+ | # apachectl | ||
+ | Syntax OK | ||
- | ===== NagVis 1.8 Installation ===== | + | 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 // | ||
+ | * **Sprache**: | ||
- | # / | + | |
- | < | + | ; |
- | | Welcome to NagVis Installer 1.8.2 | | + | ; Django : 2015-04-20 |
- | +------------------------------------------------------------------------------+ | + | ; default: unset |
- | | This script is built to facilitate the NagVis installation and update | + | language=" |
- | | procedure for you. The installer has been tested on the following systems: | | + | |
- | | - Debian, since Etch (4.0) | | + | ...</code> |
- | | - Ubuntu, since Hardy (8.04) | | + | * **Verzeichnis-Pfade**: \\ Entsprechend unserer Icinga Web 2 Konfiguration passen wir die Sektion **[paths]** an. < |
- | | - SuSE Linux Enterprise Server 10 and 11 | | + | |
- | | | | + | ; Path definitions |
- | | Similar distributions to the ones mentioned above should work as well. | | + | [paths] |
- | | That (hopefully) includes RedHat, Fedora, CentOS, OpenSuSE | + | ; absolute physical |
- | | | | + | ;base="/usr/local/nagvis/" |
- | | If you experience any problems using these or other distributions, | + | base="/usr/share/nagvis/" |
- | | report that to the NagVis team. | | + | ; absolute html NagVis path |
- | +------------------------------------------------------------------------------+ | + | ; |
- | | Do you want to proceed? [y]: y | + | ; absolute html NagVis cgi path |
- | +------------------------------------------------------------------------------+ | + | ; |
- | | Starting installation of NagVis 1.8.2 | | + | ; Django : 2015-04-20 |
- | +------------------------------------------------------------------------------+ | + | htmlcgi="/ |
- | | | | + | |
- | +--- Checking for tools -------------------------------------------------------+ | + | ...</ |
- | | Using packet manager | + | * **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, |
- | | | | + | |
- | +--- Checking | + | ; Django : 2015-04-20 |
- | | Please enter the path to the icinga base directory [/ | + | ; don't show iframe in iframe |
- | | | + | urltarget=" |
- | | Please enter the path to NagVis base [/usr/sbin/ | + | ; URL template for host object links |
- | | | | + | ; |
- | +--- Checking prerequisites ---------------------------------------------------+ | + | ; Django |
- | | PHP 5.4 found | | + | hosturl=" |
- | | PHP Module: gd php found | | + | ; URL template for hostgroup object links |
- | | PHP Module: mbstring php found | | + | ; |
- | | PHP Module: gettext compiled_in | + | ; Django |
- | | PHP Module: session compiled_in | + | hostgroupurl=" |
- | | PHP Module: xml php found | | + | ; URL template for service object links |
- | | PHP Module: pdo php found | | + | ; |
- | | | + | ; Django : 2015-04-20 |
- | | Checking Backends. (Available: mklivestatus, | + | serviceurl=" |
- | | Do you want to use backend mklivestatus? | + | ; URL template for servicegroup object links |
- | | Do you want to use backend ndo2db? | + | ; |
- | | Do you want to use backend ido2db? [n]: n | + | ; Django |
- | | | + | servicegroupurl=" |
- | | PHP Module: sockets compiled_in | + | |
- | | Graphviz 2.30 found | | + | ...</ |
- | | | + | * **Automap**: |
- | | | + | |
- | | | + | ; Options for the Automap |
- | | | + | [automap] |
- | | | + | ; Default URL parameters for links to the automap |
- | | SQLite 3.7 found | | + | ; |
- | | | | + | ; Default root host (NagVis uses this if it can't detect it via backend) |
- | +--- Trying to detect Apache settings -----------------------------------------+ | + | ; You can configure a hostname here or use "<<< |
- | | Please enter the web path to NagVis | + | ; node which shows the parent tree and all hosts which have no parents |
- | | Please enter the name of the web-server user [apache]: | + | ; defined below the is node. |
- | | Please enter the name of the web-server group [apache]: | + | ; |
- | | create Apache config file [y]: y | + | ; Path to the graphviz binaries (dot,neato,...); Only needed if not in ENV PATH |
- | | | | + | ; |
- | +--- Checking for existing NagVis ---------------------------------------------+ | + | ; Django : 2015-04-20 |
- | | | | + | defaultparams="& |
- | +------------------------------------------------------------------------------+ | + | defaultroot=" |
- | | Summary | + | graphvizpath="/ |
- | +------------------------------------------------------------------------------+ | + | |
- | | NagVis home will be: /usr/share/ | + | ...</ |
- | | Owner of NagVis files will be: apache | + | |
- | | Group of NagVis files will be: apache | + | Somit ergibt sich folgende NagVis-Konfigurations-Optionen: |
- | | Path to Apache config dir is: /etc/httpd/conf.d | | + | # egrep -v '(^\s+;|^; |
- | | Apache config will be created: yes | | + | < |
- | | | | + | file_group=" |
- | | Installation mode: | + | language=" |
- | | | | + | [paths] |
- | | Do you really want to continue? [y]: y | + | base="/ |
- | +------------------------------------------------------------------------------+ | + | htmlcgi=" |
- | | Starting installation | + | [defaults] |
- | +------------------------------------------------------------------------------+ | + | urltarget=" |
- | | Creating directory / | + | hosturl=" |
- | | Creating directory | + | hostgroupurl=" |
- | | Creating directory | + | serviceurl=" |
- | | Creating directory / | + | servicegroupurl=" |
- | | Creating directory | + | backend=" |
- | | Copying files to / | + | [index] |
- | | Creating directory / | + | [automap] |
- | | Creating main configuration file... | + | defaultparams="& |
- | | adding base="/ | + | defaultroot=" |
- | | adding htmlcgi=/ | + | graphvizpath=" |
- | | adding dbname=icinga | + | [wui] |
- | | adding dbprefix=icinga_ | + | [worker] |
- | | | + | [backend_live_1] |
- | | | + | backendtype=" |
- | | Creating web configuration file... | + | socket=" |
- | | Setting permissions for web configuration file... | + | [backend_ndomy_1] |
- | | | | + | backendtype=" |
- | | | | + | [rotation_demo] |
- | | | | + | maps=" |
- | +--- Setting permissions... ---------------------------------------------------+ | + | interval=15 |
- | | /usr/share/icinga2/ | + | [states] |
- | | / | + | |
- | | / | + | |
- | | / | + | |
- | | / | + | |
- | | /usr/share/icinga2/nagvis/etc/ | + | |
- | | /usr/share/ | + | |
- | | / | + | |
- | | / | + | |
- | | /usr/share/ | + | |
- | | /usr/share/ | + | |
- | | /usr/share/ | + | |
- | | /usr/share/ | + | |
- | | / | + | |
- | | / | + | |
- | | / | + | |
- | | /usr/share/icinga2/ | + | |
- | | | | + | |
- | +------------------------------------------------------------------------------+ | + | |
- | | Installation complete | + | |
- | | | | + | |
- | | You can safely remove this source directory. | + | |
- | | | | + | |
- | | For later update/ | + | |
- | | / | + | |
- | | | | + | |
- | | What to do next? | | + | |
- | | - Read the documentation | + | |
- | | - Maybe you want to edit the main configuration file? | | + | |
- | | Its location is: / | + | |
- | | - Configure NagVis via browser | + | |
- | | < | + | |
- | | - Initial admin credentials: | + | |
- | | | + | |
- | | | + | |
- | +------------------------------------------------------------------------------+ | + | |
</ | </ | ||
+ | Hier finden wir nochmals die komplette Konfigurationsdatei: | ||
+ | # vim / | ||
- | # | + | < |
- | < | + | ; the line above is to prevent |
- | | Welcome to NagVis | + | ; viewing this file from web. |
- | +------------------------------------------------------------------------------+ | + | ; DON'T REMOVE IT! |
- | | This script is built to facilitate | + | |
- | | procedure for you. The installer has been tested on the following systems: | + | ; ---------------------------- |
- | | - Debian, since Etch (4.0) | + | ; Default NagVis Configuration File |
- | | - Ubuntu, since Hardy (8.04) | + | ; At delivery everything here is commented out. The default values are set in the NagVis code. |
- | | - SuSE Linux Enterprise Server 10 and 11 | + | ; You can make your changes here, they' |
- | | | | + | ; ---------------------------- |
- | | Similar distributions | + | |
- | | That (hopefully) includes RedHat, Fedora, CentOS, OpenSuSE | + | ; ---------------------------- |
- | | | | + | ; !!! The sections/ |
- | | If you experience any problems using these or other distributions, please | + | ; ---------------------------- |
- | | report that to the NagVis team. | + | |
- | +------------------------------------------------------------------------------+ | + | ; General options which affect |
- | | Do you want to proceed? [y]: y | + | [global] |
- | +------------------------------------------------------------------------------+ | + | ; Enable/ |
- | | Starting installation | + | ; example user logins and logouts are logged in var/nagvis-audit.log |
- | +------------------------------------------------------------------------------+ | + | ; |
- | | | | + | ; |
- | +--- Checking | + | ; Defines the authentication module to use. By default NagVis uses the built-in |
- | | Using packet manager / | + | ; SQLite authentication module. On delivery there is no other authentication |
- | | | | + | ; module available. It is possible to add own authentication modules for |
- | +--- Checking paths -----------------------------------------------------------+ | + | ; supporting other authorisation mechanisms. For details take a look at the |
- | | Please enter the path to the nagios base directory | + | ; documentation. |
- | | | + | ; |
- | | Please enter the path to NagVis | + | ; |
- | | | | + | ; Defines the authorisation module |
- | +--- Checking prerequisites ---------------------------------------------------+ | + | ; SQLite authorisation module. On delivery there are some other modules available: |
- | | PHP 5.4 found | | + | ; |
- | | PHP Module: gd php found | | + | ; - CoreAuthorisationModMySQL: |
- | | PHP Module: mbstring php found | | + | ; |
- | | | + | ; - CoreAuthorisationModMultisite: |
- | | | + | ; to gather user permissions. This makes use of the roles defined for a user within |
- | | | + | ; |
- | | | + | ; - CoreAuthorisationModGroups: |
- | | | + | ; |
- | | Do you want to update | + | ; |
- | | Checking Backends. (Available: mklivestatus,ndo2db, | + | ; |
- | | Do you want to use backend mklivestatus? | + | ; group within |
- | | Do you want to use backend ndo2db? [n]: n | + | ; |
- | | Do you want to use backend ido2db? [n]: n | + | ; It is possible to add own authorisation modules |
- | | | + | ; mechanisms. For details take a look at the documentation. |
- | | PHP Module: sockets compiled_in | + | ; |
- | | Graphviz 2.30 found | | + | ; |
- | | | + | ; If you use CoreAuthorisationModGroups above, you might need these options: |
- | | | + | ; This option defines |
- | | | + | ; is searched within |
- | | | + | ; |
- | | | + | ; This option is used to configure one or several backend_ids, |
- | | SQLite 3.7 found | | + | ; should be used to get the users contact group memberships from. |
- | | | | + | ; |
- | +--- Trying | + | ; |
- | | Please enter the web path to NagVis | + | ; Sets the size of the controls in unlocked (edit) mode of the frontend. This |
- | | Please enter the name of the web-server user [apache]: | + | ; defaults to a value of 10 which makes each control be sized to 10px * 10px. |
- | | Please enter the name of the web-server group [apache]: | + | ; |
- | | create Apache config file [y]: n | + | ; |
- | | | | + | ; Dateformat of the time/dates shown in nagvis (For valid format see PHP docs) |
- | +--- Checking | + | ; |
- | | NagVis 1.8.2 found | | + | ; |
- | | Do you want the installer to update your config files when possible? | + | ; Used to configure |
- | | Remove backup directory after successful installation? | + | ; dialog_ack_sticky=1 |
- | | | | + | ; dialog_ack_notify=1 |
- | +------------------------------------------------------------------------------+ | + | ; dialog_ack_persist=0 |
- | | Summary | + | ; |
- | +------------------------------------------------------------------------------+ | + | ; File group and mode are applied |
- | | NagVis home will be: /usr/share/nagvis | + | ; Usualy these values can be left as they are. In some rare cases you might |
- | | Owner of NagVis files will be: apache | + | ; want to change these values to make the files writeable/readable by some other |
- | | Group of NagVis files will be: apache | + | ; users in a group. |
- | | Path to Apache config dir is: | + | file_group=" |
- | | Apache config will be created: NO | | + | ; |
- | | | | + | ; |
- | | Installation mode: | + | ; The server to use as source for the NagVis geomaps. Must implement the API which |
- | | Old version: 1.8.2 | + | ; can be found on http://pafciu17.dev.openstreetmap.org/ |
- | | New version: 1.8.2 | + | ; |
- | | Backup directory: /usr/share/nagvis.old-2015-04-20_10: | + | ; |
- | | | | + | ; In some cases NagVis needs to open connections to the internet. The cases are: |
- | | Note: The current NagVis directory will be moved to the backup directory. | + | ; - The new geomap needs access to openstreetmap webservices to be able to fetch |
- | | The backup directory will be NOT removed after successful installation | | + | ; |
- | | Your configuration files will be copied. | | + | ; Most company networks don't allow direct HTTP access to the internet. The most |
- | | The configuration files will be updated if possible. | | + | ; 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 |
- | | Do you really want to continue? [y]: y | + | ; is " |
- | +------------------------------------------------------------------------------+ | + | ; |
- | | Starting installation | + | ; Most proxies require authentication to access the internet. Use the format |
- | +------------------------------------------------------------------------------+ | + | ; "< |
- | | Moving old NagVis | + | ; |
- | | Creating directory / | + | ; Set the timeout (in seconds) for outbound HTTP requests (for example geomap requests) |
- | | Creating directory / | + | ; |
- | | Creating directory /usr/share/ | + | ; |
- | | Creating directory | + | ; Defines which translations of NagVis are available to the users |
- | | Creating directory / | + | ; |
- | | Copying files to / | + | ; Language detection steps to use. Available: |
- | | Creating directory | + | ; |
- | | Creating main configuration | + | ; |
- | | adding base="/ | + | ; |
- | | | + | ; |
- | | | + | ; |
- | | *** creation of /etc/httpd/conf.d/ | + | ; |
- | | | | + | ; |
- | | Restoring main configuration file(s)... | + | ; Select language (Available by default: en_US, de_DE, fr_FR, pt_BR) |
- | | Restoring custom map configuration files... | + | ; |
- | | Restoring custom geomap source files... | + | ; Django : 2015-04-20 |
- | | Restoring user configuration files... | + | ; default: unset |
- | | Restoring conf.d/ configuration files... | + | language=" |
- | | Restoring | + | ; |
- | | Restoring custom gadget images... | + | ; Defines the logon module to use. There are three logon modules to be used by |
- | | Restoring custom iconsets... | + | ; default. It is possible to add own logon modules for serving other dialogs or |
- | | Restoring custom shapes... | + | ; ways of logging in. For details take a look at the documentation. |
- | | Restoring custom templates... | + | ; |
- | | Restoring custom template images... | + | ; The delivered modules are: |
- | | Restoring custom gadgets... | + | ; |
- | | Restoring custom scripts... | + | ; LogonMixed: The mixed logon module uses the LogonEnv module as default and |
- | | Restoring auth database file... | + | ; |
- | | Restoring | + | ; |
- | | | | + | ; |
- | +------------------------------------------------------------------------------+ | + | ; LogonDialog: This is an HTML logon dialog for requesting authentication |
- | | Handling changed/ | + | ; |
- | +------------------------------------------------------------------------------+ | + | ; |
- | | Removing allowedforconfig option from main config... | + | ; LogonEnv: It is possible to realise a fully " |
- | | Removing autoupdatefreq option from main config... | + | ; |
- | | Removing htmlwuijs option from main config... done | | + | ; |
- | | Removing wuijs option from main config... done | | + | ; |
- | | Removing showautomaps option from main config... | + | ; user. You can add several authentication mechanisms to your webserver, |
- | | Removing usegdlibs option from main config... done | | + | ; |
- | | Removing displayheader option from main config... done | | + | ; |
- | | Removing hovertimeout option from main config... | + | ; |
- | | Removing allowed_for_config option from map configs... | + | ; |
- | | Removing allowed_user from map configs... done | | + | ; |
- | | Removing hover_timeout from map configs... | + | ; |
- | | Removing usegdlibs from map configs... | + | ; set to empty string to disable that behaviour. |
- | +------------------------------------------------------------------------------+ | + | ; |
- | | HINT: Please check the changelog or the documentation for changes which | | + | ; LogonMultisite: This module uses the authentication provided by auth_* cookies |
- | | | + | ; which have been generated by Check_MK multisite when using the cookie based |
- | | | | + | ; |
- | +--- Setting permissions... ---------------------------------------------------+ | + | ; to use this, you need to define a new option called logon_multisite_serials |
- | | /usr/share/nagvis/etc/ | + | ; |
- | | /usr/share/nagvis/etc done | + | ; |
- | | /usr/share/nagvis/ | + | ; |
- | | /usr/share/nagvis/etc/maps/ | + | ; |
- | | /usr/share/nagvis/etc/ | + | ; |
- | | /usr/share/nagvis/ | + | ; |
- | | /usr/share/nagvis/etc/profiles | + | ; |
- | | /usr/share/nagvis/etc/ | + | ; |
- | | /usr/share/nagvis/share/ | + | ; |
- | | / | + | ; |
- | | / | + | ; |
- | | / | + | ; |
- | | / | + | ; |
- | | / | + | ; |
- | | / | + | ; Default rotation time of pages in rotations |
- | | / | + | ; |
- | | /usr/share/nagvis/ | + | ; |
- | | /usr/share/nagvis/ | + | ; 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. |
- | | Installation complete | + | ; Domain to set the cookie for. By default NagVis tries to auto-detect this |
- | | | | + | ; options value by using the webserver' |
- | | You can safely remove this source directory. | | + | ; |
- | | | | + | ; Absolute web path to set the cookie for. This defaults to configured |
- | | For later update/ | + | ; paths/ |
- | | ./ | + | ; |
- | | | | + | ; Lifetime of the NagVis session cookie in seconds. The default value is set to |
- | | What to do next? | + | ; 24 hours. The NagVis session cookie contents will be renewed on every page |
- | | - Read the documentation | + | ; visit. If a session is idle for more time than configured here it will become |
- | | - Maybe you want to edit the main configuration file? | | + | ; invalid. |
- | | Its location is: / | + | ; |
- | | - Configure NagVis via browser | + | ; Most modern browsers will deny javascript access to cookies if the HttpOnly |
- | | <http:// | + | ; flag is set. This prevents XSS attacks from stealing cookies. Default is off |
- | | - Initial | + | ; to not break any existing installations that rely on this functionality. Set |
- | | | + | ; to 1 to enable. |
- | | | + | ; |
- | +------------------------------------------------------------------------------+ | + | ; 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. | ||
+ | ; | ||
+ | ; | ||
+ | ; Staleness threshold (Only used with livestatus backend). Take a look at the | ||
+ | ; Check_MK documentation for details about the staleness of hosts/ | ||
+ | ; 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. | ||
+ | ; | ||
+ | ; | ||
+ | ; Start page to redirect the user to when first visiting NagVis without | ||
+ | ; special parameters. | ||
+ | ; | ||
+ | ; | ||
+ | ; The startshow parameter is only used by some views at the moment. It is used | ||
+ | ; by the Map module. | ||
+ | ; | ||
+ | ; | ||
+ | ; 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 " | ||
+ | ; | ||
+ | |||
+ | ; Path definitions | ||
+ | [paths] | ||
+ | ; absolute physical NagVis path | ||
+ | ; | ||
+ | base="/ | ||
+ | ; absolute html NagVis path | ||
+ | ; | ||
+ | ; absolute html NagVis cgi path | ||
+ | ; | ||
+ | ; Django : 2015-04-20 | ||
+ | htmlcgi="/ | ||
+ | |||
+ | ; Default values which get inherited to the maps and its objects | ||
+ | [defaults] | ||
+ | ; default backend (id of the default backend) | ||
+ | ; | ||
+ | ; background color of maps | ||
+ | ; | ||
+ | ; Enable/ | ||
+ | ; able to bind commands or links to your map objects | ||
+ | ; | ||
+ | ; Choose the default context template | ||
+ | ; | ||
+ | ; Raise frontend events for problematic objects also on page loading. Set to 1 to | ||
+ | ; enable this feature | ||
+ | ; | ||
+ | ; Repeat frontend events in the given interval. The interval is configured in seconds. | ||
+ | ; | ||
+ | ; 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. | ||
+ | ; | ||
+ | ; Enable/ | ||
+ | ; shown when summary state is PENDING, OK or UP) | ||
+ | ; | ||
+ | ; Enable/ | ||
+ | ; border | ||
+ | ; | ||
+ | ; The duration of the event highlight in milliseconds (10 seconds by default) | ||
+ | ; | ||
+ | ; The interval of the event highlight in milliseconds (0.5 seconds by default) | ||
+ | ; | ||
+ | ; Enable/ | ||
+ | ; track of important actions and information | ||
+ | ; | ||
+ | ; Loglevel of the eventlog (available: debug, info, warning, critical) | ||
+ | ; | ||
+ | ; Number of events kept in the scrollback | ||
+ | ; | ||
+ | ; Height of the eventlog when visible in px | ||
+ | ; | ||
+ | ; Hide/Show the eventlog on page load | ||
+ | ; | ||
+ | ; Enable/ | ||
+ | ; out of the visible scope | ||
+ | ; | ||
+ | ; Enable/ | ||
+ | ; | ||
+ | ; enable/ | ||
+ | ; | ||
+ | ; header template | ||
+ | ; | ||
+ | ; Enable/ | ||
+ | ; | ||
+ | ; Show states in the sidebar header menu (if supported by template) | ||
+ | ; | ||
+ | ; enable/ | ||
+ | ; | ||
+ | ; hover template | ||
+ | ; | ||
+ | ; hover menu open delay (seconds) | ||
+ | ; | ||
+ | ; show children in hover menus | ||
+ | ; | ||
+ | ; limit shown child objects to n | ||
+ | ; | ||
+ | ; order method of children (desc: descending, asc: ascending) | ||
+ | ; | ||
+ | ; sort method of children (s: state, a: alphabetical) | ||
+ | ; | ||
+ | ; default icons | ||
+ | ; | ||
+ | ; recognize only hard states (not soft) | ||
+ | ; | ||
+ | ; recognize service states in host/ | ||
+ | ; | ||
+ | ; show map in lists (dropdowns, index page, ...) | ||
+ | ; | ||
+ | ; show map in multisite snapin | ||
+ | ; | ||
+ | ; Name of the custom stylesheet to use on the maps (The file needs to be located | ||
+ | ; in the share/ | ||
+ | ; | ||
+ | ; target for the icon links | ||
+ | ; | ||
+ | ; Django : 2015-04-20 | ||
+ | ; don't show iframe in iframe | ||
+ | urltarget=" | ||
+ | ; URL template for host object links | ||
+ | ; | ||
+ | ; Django : 2015-04-20 | ||
+ | hosturl=" | ||
+ | ; URL template for hostgroup object links | ||
+ | ; | ||
+ | ; Django : 2015-04-20 | ||
+ | hostgroupurl=" | ||
+ | ; URL template for service object links | ||
+ | ; | ||
+ | ; Django : 2015-04-20 | ||
+ | serviceurl=" | ||
+ | ; URL template for servicegroup object links | ||
+ | ; | ||
+ | ; Django : 2015-04-20 | ||
+ | servicegroupurl=" | ||
+ | ; URL template for dynamic group object links (disabled by default) | ||
+ | ; | ||
+ | ; URL template for aggregations object links (disabled by default) | ||
+ | ; | ||
+ | ; URL template for nested map links | ||
+ | ; | ||
+ | ; Templates to be used for the different views. | ||
+ | ; | ||
+ | ; Enable/ | ||
+ | ; | ||
+ | ; Configure the colors used by weathermap lines | ||
+ | ; | ||
+ | ; Show mouse controllable elements for zooming | ||
+ | ; | ||
+ | ; 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 | ||
+ | ; | ||
+ | |||
+ | ; Options to configure the Overview page of NagVis | ||
+ | backend=" | ||
+ | [index] | ||
+ | ; Color of the overview background | ||
+ | ; | ||
+ | ; Set number | ||
+ | ; | ||
+ | ; enable/ | ||
+ | ; | ||
+ | ; header template | ||
+ | ; | ||
+ | ; Enable/ | ||
+ | ; | ||
+ | ; Enable/ | ||
+ | ; | ||
+ | ; Enable/ | ||
+ | ; | ||
+ | |||
+ | ; Options for the Automap | ||
+ | [automap] | ||
+ | ; Default URL parameters | ||
+ | ; | ||
+ | ; Default root host (NagVis | ||
+ | ; You can configure a hostname here or use "<<< | ||
+ | ; node which shows the parent tree and all hosts which have no parents | ||
+ | ; defined below the is node. | ||
+ | ; | ||
+ | ; Path to the graphviz binaries (dot, | ||
+ | ; | ||
+ | ; Django : 2015-04-20 | ||
+ | defaultparams="& | ||
+ | defaultroot=" | ||
+ | graphvizpath="/ | ||
+ | |||
+ | ; 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. | ||
+ | ; | ||
+ | ; Show/hide the grid | ||
+ | ; | ||
+ | ; The color of the grid lines | ||
+ | ; | ||
+ | ; The space between the single grid lines in pixels | ||
+ | ; | ||
+ | |||
+ | ; Options for the new Javascript worker | ||
+ | [worker] | ||
+ | ; The interval in seconds in which the worker will check for objects which need | ||
+ | ; to be updated | ||
+ | ; | ||
+ | ; The maximum number of parameters used in ajax http requests | ||
+ | ; Some intrusion detection/ | ||
+ | ; too many parameters in the url. Give 0 for no limit. | ||
+ | ; | ||
+ | ; The maximum length of http request urls during ajax http requests | ||
+ | ; Some intrusion detection/ | ||
+ | ; queries being too long | ||
+ | ; | ||
+ | ; The retention time of the states in the frontend in seconds. The state | ||
+ | ; information will be refreshed after this time | ||
+ | ; | ||
+ | |||
+ | ; ---------------------------- | ||
+ | ; Backend definitions | ||
+ | ; ---------------------------- | ||
+ | |||
+ | ; Example definition of a livestatus backend. | ||
+ | ; In this case the backend_id is live_1 | ||
+ | ; The path /usr/local/nagios/ | ||
+ | [backend_live_1] | ||
+ | backendtype=" | ||
+ | ; The status host can be used to prevent annoying timeouts when a backend | ||
+ | ; reachable. This is only useful in multi backend setups. | ||
+ | ; | ||
+ | ; It works as follows: The assumption is that there is a " | ||
+ | ; monitors the host of the " | ||
+ | ; reported as UP the backend is queried as normal. | ||
+ | ; When the remote backend host is reported as " | ||
+ | ; try to connect to the backend anymore until the backend host gets available again. | ||
+ | ; | ||
+ | ; The statushost needs to be given in the following format: | ||
+ | ; "< | ||
+ | ; | ||
+ | socket=" | ||
+ | |||
+ | ; Example definition for a MySQL backend | ||
+ | ; in this example the ID of the Backend is " | ||
+ | [backend_ndomy_1] | ||
+ | ; type of backend - MUST be set | ||
+ | backendtype=" | ||
+ | ; 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: | ||
+ | ; monitors the host of the " | ||
+ | ; reported as UP the backend is queried as normal. | ||
+ | ; When the remote backend host is reported as " | ||
+ | ; try to connect to the backend anymore until the backend host gets available again. | ||
+ | ; | ||
+ | ; The statushost needs to be given in the following format: | ||
+ | ; "< | ||
+ | ; | ||
+ | ; hostname for NDO-db | ||
+ | ; | ||
+ | ; portname for NDO-db | ||
+ | ; | ||
+ | ; database name for NDO-db | ||
+ | ; | ||
+ | ; username for NDO-db | ||
+ | ; | ||
+ | ; password for NDO-db | ||
+ | ; | ||
+ | ; prefix for tables in NDO-db | ||
+ | ; | ||
+ | ; instance name for tables in NDO-db | ||
+ | ; | ||
+ | ; maximum delay of the NDO Database in seconds | ||
+ | ; | ||
+ | ; path to the cgi-bin of this backend | ||
+ | ; | ||
+ | |||
+ | ; ---------------------------- | ||
+ | ; 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] | ||
+ | ; These steps are rotated. The single steps may have optional prefixes like " | ||
+ | ; 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=" | ||
+ | ; rotation interval (seconds) | ||
+ | interval=15 | ||
+ | |||
+ | ; ---------------------------- | ||
+ | ; Action definitions | ||
+ | ; ---------------------------- | ||
+ | ; Since NagVis | ||
+ | ; 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 " | ||
+ | ; 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 " | ||
+ | ; on the clients which have a listed operating system running. | ||
+ | |||
+ | ; Adds the action " | ||
+ | ; has the string " | ||
+ | ; When clicking on the link, NagVis generates a .rdp file which contains makes | ||
+ | ; the client connect | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | |||
+ | ; Adds the action " | ||
+ | ; string " | ||
+ | ; 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. | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | |||
+ | ; Adds the action " | ||
+ | ; string " | ||
+ | ; detects that the client watching the map uses linux or mac os. | ||
+ | ; When clicking on the link, the browser opens the URL ssh://< | ||
+ | ; you need to configure your clients browser to handle these urls correctly. | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | |||
+ | ; Adds the action " | ||
+ | ; string " | ||
+ | ; When clicking on the link, the browser opens a new window with the URL | ||
+ | ; http://< | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | |||
+ | ; Adds the action " | ||
+ | ; string " | ||
+ | ; When clicking on the link, the browser opens a new window with the URL | ||
+ | ; https://< | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | |||
+ | ; ------------------------------------------------------------------------------ | ||
+ | ; Below you find some advanced stuff | ||
+ | ; ------------------------------------------------------------------------------ | ||
+ | |||
+ | ; Configure different state related settings | ||
+ | [states] | ||
+ | ; State coverage/ | ||
+ | ; 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. | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ;error=4 | ||
+ | ; | ||
+ | ; | ||
+ | ;up=2 | ||
+ | ;ok=1 | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; 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 | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; 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. | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | |||
+ | ; ------------------------- | ||
+ | ; EOF | ||
+ | ; ------------------------- | ||
+ | </ | ||
+ | |||
+ | |||
+ | |||
+ | ===== Icinga Web 2 Modul ===== | ||
+ | ==== Installation ==== | ||
+ | Für das Einbetten der NagVis-Karten in **Icinga Web2** greifen wir auf das Modul **[[https:// | ||
+ | |||
+ | Als erstes holen wir uns das Modul von der **[[https://github.com/divetoh/icingaweb2-module-nagvis|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/ | ||
+ | |||
+ | ==== 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**. | ||
+ | |||
+ | {{ :centos: | ||
+ | |||
+ | Einen ersten Eindruck können wir uns mit Hilfe der bei der Erstinstallation angelegten Demo-Karten verschaffen. | ||
+ | |||
+ | {{ :centos: | ||
+ | |||
+ | |||
+ | |||
+ | ===== 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// | ||
- | ==== muell ==== | + | Zu guter Letzt ändern wir das Standardpasswort des Accounts **admin** noch ab. Dazu wählen wir aus dem **Nutzermenü** rechts oben den Menüpunkt **// |
- | + | {{ :centos: | |
- | Diese Anweisungen gelten für eine Neuinstallation. | + | |
- | Wenn Sie Ihre alte NagVis-Installation aktualisieren, | + | |
- | SCHRITT 0: das System vorbereiten | + | |
- | Stellen Sie sicher, dass Ihr System den Systemanforderungen entspricht. | + | |
- | SCHRITT 1: NagVis herunterladen | + | |
- | Holen Sie sich NagVis, die neueste Version finden Sie unter www.nagvis.org. | + | |
- | SCHRITT | + | |
- | tar xvzf nagvis-1.8.x.tar.gz | + | Nach Eingabe des alten Passwortes **admin** tragen wir 2x unser neues Passwort ein und klicken dann auf die Schaltfläche **Passwort ändern**. |
- | SCHRITT 3: verschieben Sie das entpackte NagVis-Verzeichnis | + | {{ :centos: |
- | Platzieren Sie den NagVis-Verzeichnisbaum irgendwo in Ihrem System. In den meisten Fällen ist / | + | |
- | mv nagvis-1.8.x / | + | ==== 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__**, | ||
- | Sie sollten mindestens die folgenden Dateien und Verzeichnisse unter dem nagvis-Verzeichnis | + | Als erstes legen wir uns das Backup-Verzeichnis |
+ | # mkdir / | ||
- | ls -l /usr/local/nagvis | + | Dann verschieben wir die map-Konfigurationsdateien in dieses Verzeichnis. |
- | | + | # mv /usr/share/nagvis/etc/maps/* / |
- | LICENSE | + | |
- | README | + | |
- | share | + | |
- | var | + | |
- | Verschieben Sie KEINE Dateien oder Verzeichnisse innerhalb | + | Abschließend deaktivieren wir noch die Parameter |
- | SCHRITT 4: konfigurieren Sie NagVis | + | # vim / |
- | Wechseln Sie zur neuen Position des NagVis-Verzeichnisses | + | |
- | cd / | + | < |
- | Eine Beispiel-Hauptkonfigurationsdatei finden Sie als etc/ | + | ; ---------------------------- |
+ | ; Rotation pool definitions | ||
+ | ; ---------------------------- | ||
- | cp etc/ | + | ; in this example the browser switches between the maps demo and demo2 every 15 |
+ | ; seconds, the rotation is enabled by url: index.php? | ||
+ | ; Django : 2015-04-20 | ||
+ | ; default: [rotation_demo] | ||
+ | ; These steps are rotated. The single steps may have optional prefixes like " | ||
+ | ; 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=" | ||
+ | ; rotation interval (seconds) | ||
+ | ; Django : 2015-04-20 | ||
+ | ; default: interval=15 | ||
- | Nun können Sie dieses Datei mit Ihrem bevorzugten Texteditor ändern � ich benutze vi: | + | ...</ |
- | vi etc/nagvis.ini.php | + | ==== Automap ==== |
+ | Im folgendem Konfigurationsbeispiel, | ||
- | Die meisten Zeilen in der frisch kopierten nagvis.ini.php sind auskommentiert (beginnen mit einem Semikolon). Wenn Sie verschiedene Einstellungen setzen möchten, dann entfernen Sie das Kommentarzeichen und ändern Sie den Wert. | + | Als erstes wählen wir aus dem NagVis-Menü **Optionen** den Menüpunkt |
- | Informationen zu allen möglichen Werten finden Sie in der Formatbeschreibung der Hauptkonfigurationsdatei. | + | |
- | SCHRITT 5: konfigurieren des Web-Servers | + | |
- | Seit NagVis 1.5 ist es notwendig, den Web-Server zu konfigurieren, | + | {{ : |
- | Kopieren Sie einfach die Datei in das conf.d-Verzeichnis Ihres Web-Servers. Dies ist z.B. / | + | |
- | cp etc/apache2-nagvis.conf-sample / | + | Hier wählen wir dann die **Standard-Datenquelle** aus und klicken anschließend auf die Schaltfläche **Speichern**. |
- | Nun müssen Sie die Datei öffnen und auf Ihre Anforderungen anpassen. Es ist wichtig, die Makros @NAGVIS_WEB@ und @NAGVIS_PATH@ durch die korrekten Werte zu ersetzen. | + | {{ : |
- | In diesem Beispiel müssen Sie @NAGVIS_WEB@ durch /nagvis und @NAGVIS_PATH@ durch / | + | |
- | SCHRITT 6: Berechtigungen | + | Nun definieren wir uns eine eigene Karte vom Typ **automap**; |
- | Dies ist sehr wichtig für eine funktionierende Installation. | + | |
- | Prüfen Sie zuerst, welcher Unix-Account für Ihren Webserver benutzt wird (in meinem Fall wwwrun). Wenn Sie nicht wissen, mit welchem Benutzer der Webserver läuft, dann werfen Sie einen Blick in die Webserver-Konfiguration. Im Falle von Apache können Sie dies mit dem folgenden Befehl tun: | + | {{ : |
- | Ubuntu | + | Zum Generieren der Automap befüllen wir beim Menüpunkt **Karte erstellen** die Felder **//ID (Interner Name)//** und **// |
- | grep -e ' | + | {{ : |
- | SuSE/ | + | Basieren auf den Monitoringkonfiguration unserer **Icinga 2** Umgebung wird nach einer kurzen Zeit die generierte **automap** angezeigt. |
- | grep -e ' | + | {{ : |
- | Wenn Ihre Konfigurationsdatei an anderer Stelle liegt, dann passen Sie den obigen Befehl an. | + | Sobald wir mit der Maus übe einen der überwachten Host streichen, werden weitere Details des Hosts eingeblendet. |
- | Gewähren Sie nun dem Webserver-Benutzer Berechtigungen für das NagVis-Verzeichnis (in meinem Fall sind die Pfade wie folgt): | + | |
- | chown wwwrun:www / | + | {{ :centos: |
- | chmod 664 / | + | |
- | chmod 775 / | + | |
- | chmod 664 / | + | |
- | chmod 775 / | + | |
- | chmod 664 / | + | |
- | chmod 775 / | + | |
- | chmod 664 / | + | |
- | chmod 775 / | + | |
- | chmod 664 / | + | |
- | chmod 775 / | + | |
- | chmod 664 / | + | |
- | Es ist möglich, restriktivere Berechtigungen für die Dateien zu setzen, aber für die meisten Setups sollten die Beispiele ausreichen. Verändern Sie die Werte nur dann, wenn Sie wissen, was Sie tun! | + | Klicken wir auf einen Host, gelangen wir direkt auf die Icinga Web 2 Detailseite des Hosts. |
- | SCHRITT 7: konfigurieren Sie die Maps | + | |
- | Es gibt zwei Wege, NagVis zu konfigurieren. Der erste ist die web-basierte Konfiguration mit Hilfe des NagVis-Frontends (http://< | + | {{ : |
- | Beim zweiten Weg bearbeiten Sie direkt die Konfigurationsdateien mit dem Text-Editor Ihrer Wahl. Die Map-Konfigurationsdateien befinden sich in etc/maps/. Gültige Formate und Werte finden Sie unter Map Config Format Description. | ||
- | SCHRITT 8: betrachten Sie die Maps | ||
- | Sie sollten nun in der Lage sein, Ihre definierten Maps in Ihrem Browser anzusehen: | ||
- | http://< | + | ====== Links ====== |
+ | * **⇐ [[centos:web_c7: | ||
+ | * **[[centos: | ||
+ | * **[[wiki: | ||
+ | * **[[http://dokuwiki.nausch.org/doku.php/ | ||
- | (z.B. http:// | ||
- | Viel Spaß und bitte melden Sie Bugs! |