NagVis - Présentation et installation

Cet article présente NagVis et en montre l'installation.

 

 

Connexion de NagVis à Icinga/Shinken/Nagios

( default  --> /usr/share/doc/check_mk/checks):

working directory of check_mk
check_mk will create caches files, automatically created checks and
other files into this directory. The setup will create several subdirectories
and makes them writable by the Nagios process:
( default  --> /var/lib/check_mk):



  2) Configuration of Linux/UNIX Agents


extensions for agents
This directory will not be created on the server. It will be hardcoded
into the Linux and UNIX agents. The agent will look for extensions in the
subdirectories plugins/ and local/ of that directory:
( default  --> /usr/lib/check_mk_agent):

configuration dir for agents
This directory will not be created on the server. It will be hardcoded
into the Linux and UNIX agents. The agent will look for its configuration
files here (currently only the logwatch extension needs a configuration file):
( default  --> /etc/check_mk):



  3) Integration with Nagios


Name of Nagios user
The working directory for check_mk contains several subdirectories
that need to be writable by the Nagios user (which is running check_mk
in check mode). Please specify the user that should own those
directories:
( autodetected  --> nagios):

User of Apache process
Check_MK WATO (Web Administration Tool) needs a sudo configuration,
such that Apache can run certain commands as root. If you specify
the correct user of the apache process here, then we can create a valid
sudo configuration for you later::
( autodetected  --> apache):

Common group of Nagios+Apache
Check_mk creates files and directories while running as nagios.
Some of those need to be writable by the user that is running the webserver.
Therefore a group is needed in which both Nagios and the webserver are
members (every valid Nagios installation uses such a group to allow
the web server access to Nagios' command pipe)::
( default  --> nagios):

Nagios binary
The complete path to the Nagios executable. This is needed by the
option -R/--restart in order to do a configuration check.:
( autodetected  --> /usr/local/nagios/bin/nagios):

Nagios main configuration file
Path to the main configuration file of Nagios. That file is always
named 'nagios.cfg'. The default path when compiling Nagios yourself
is /usr/local/nagios/etc/nagios.cfg. The path to this file is needed
for the check_mk option -R/--restart:
( autodetected  --> /usr/local/nagios/etc/nagios.cfg):

Nagios object directory
Nagios' object definitions for hosts, services and contacts are
usually stored in various files with the extension .cfg. These files
are located in a directory that is configured in nagios.cfg with the
directive 'cfg_dir'. Please specify the path to that directory
(If the autodetection can find your configuration
file but does not find at least one cfg_dir directive, then it will
add one to your configuration file for your conveniance):
( autodetected  --> /usr/local/nagios/etc/check_mk.d):

Nagios startskript
The complete path to the Nagios startskript is used by the option
-R/--restart to restart Nagios.:
( autodetected  --> /etc/init.d/nagios):

Nagios command pipe
Complete path to the Nagios command pipe. check_mk needs write access
to this pipe in order to operate:
( autodetected  --> /usr/local/nagios/var/rw/nagios.cmd):

Check results directory
Complete path to the directory where Nagios stores its check results.
Using that directory instead of the command pipe is faster.:
( autodetected  --> /usr/local/nagios/var/spool/checkresults):

Nagios status file
The web pages of check_mk need to read the file 'status.dat', which is
regularily created by Nagios. The path to that status file is usually
configured in nagios.cfg with the parameter 'status_file'. If
that parameter is missing, a compiled-in default value is used. On
FHS-conforming installations, that file usually is in /var/lib/nagios
or /var/log/nagios. If you've compiled Nagios yourself, that file
might be found below /usr/local/nagios:
( autodetected  --> /usr/local/nagios/var/status.dat):

Path to check_icmp
check_mk ships a Nagios configuration file with several host and
service templates. Some host templates need check_icmp as host check.
That check plugin is contained in the standard Nagios plugins.
Please specify the complete path (dir + filename) of check_icmp:
( autodetected  --> /usr/local/nagios/libexec/check_icmp):



  4) Integration with Apache


URL Prefix for Web addons
Usually the Multisite GUI is available at /check_mk/ and PNP4Nagios
is located at /pnp4nagios/. In some cases you might want to define some
prefix in order to be able to run more instances of Nagios on one host.
If you say /test/ here, for example, then Multisite will be located
at /test/check_mk/. Please do not forget the trailing slash.:
( default  --> /):

Apache config dir
Check_mk ships several web pages implemented in Python with Apache
mod_python. That module needs an apache configuration section which
will be installed by this setup. Please specify the path to a directory
where Apache reads in configuration files.:
( autodetected  --> /etc/httpd/conf.d):

HTTP authentication file
Check_mk's web pages should be secured from unauthorized access via
HTTP authenticaion - just as Nagios. The configuration file for Apache
that will be installed contains a valid configuration for HTTP basic
auth. The most conveniant way for you is to use the same user file as
for Nagios. Please enter your htpasswd file to use here:
( autodetected  --> /usr/local/nagios/etc/htpasswd.users):

HTTP AuthName
Check_mk's Apache configuration file will need an AuthName. That
string will be displayed to the user when asking for the password.
You should use the same AuthName as for Nagios. Otherwise the user will
have to log in twice:
( autodetected  --> Nagios Access):



  5) Integration with PNP4Nagios 0.6


PNP4Nagios templates
Check_MK ships templates for PNP4Nagios for most of its checks.
Those templates make the history graphs look nice. PNP4Nagios
expects such templates in the directory pnp/templates in your
document root for static web pages:
( default  --> /usr/share/check_mk/pnp-templates):



  6) Check_MK Livestatus Module


compile livestatus module
The well known MK Livestatus broker module is part of Check_MK.

It provides direct access to Nagios internal data structures. It aims to
supersede status.dat and also NDO. The Livestatus Module does not only
allow extremely fast access to the status of your services and hosts, it
does also provide live data (which status.dat does not). Also - unlike NDO -
Livestatus does not cost you even measurable CPU performance, does not need
any disk space and also needs no configuration.

Livestatus is neccessary when you want to use Multisite. It is also
the preferred backend for NagVis.

Please answer 'yes', if you want to compile and integrate the
Livestatus module into your Nagios. You need 'make' and the GNU
C++ compiler installed in order to do this:
( default  --> yes):

check_mk's binary modules
Directory for architecture dependent binary libraries and plugins
of check_mk:
( default  --> /usr/lib/check_mk):

Unix socket for Livestatus
The Livestatus Module provides Nagios status data via a unix
socket. This is similar to the Nagios command pipe, but allows
bidirectional communication. Please enter the path to that pipe.
It is recommended to put it into the same directory as Nagios'
command pipe:
( default  --> /usr/local/nagios/var/rw/live):

Backends for other systems
Directory where to put backends and configuration examples for
other systems. Currently this is only Nagvis, but other might follow
later.:
( default  --> /usr/share/check_mk/livestatus):



  7) Check_MK Event Console


Install Event Console
The Check_MK Event Console is a full featured event processing
module that integrates with Multisite. It has an own daemon and
several methods for retrieving events. It even has an integrated
syslog daemon.  Please answer 'yes', if you want to enable the
Event Console.:
( default  --> no): yes

working directory of mkeventd
The Event Console Daemon will store status and historic data in this
directory.:
( default  --> /var/lib/mkeventd):


----------------------------------------------------------------------

You have chosen the following directories:

 Executable programs             /usr/bin
 Check_MK configuration          /etc/check_mk
 Check_MK software               /usr/share/check_mk
 documentation                   /usr/share/doc/check_mk
 check manuals                   /usr/share/doc/check_mk/checks
 working directory of check_mk   /var/lib/check_mk
 extensions for agents           /usr/lib/check_mk_agent
 configuration dir for agents    /etc/check_mk
 Name of Nagios user             nagios
 User of Apache process          apache
 Common group of Nagios+Apache   nagios
 Nagios binary                   /usr/local/nagios/bin/nagios
 Nagios main configuration file  /usr/local/nagios/etc/nagios.cfg
 Nagios object directory         /usr/local/nagios/etc/check_mk.d
 Nagios startskript              /etc/init.d/nagios
 Nagios command pipe             /usr/local/nagios/var/rw/nagios.cmd
 Check results directory         /usr/local/nagios/var/spool/checkresults
 Nagios status file              /usr/local/nagios/var/status.dat
 Path to check_icmp              /usr/local/nagios/libexec/check_icmp
 URL Prefix for Web addons       /
 Apache config dir               /etc/httpd/conf.d
 HTTP authentication file        /usr/local/nagios/etc/htpasswd.users
 HTTP AuthName                   Nagios Access
 PNP4Nagios templates            /usr/share/check_mk/pnp-templates
 compile livestatus module       yes
 check_mk's binary modules       /usr/lib/check_mk
 Unix socket for Livestatus      /usr/local/nagios/var/rw/live
 Backends for other systems      /usr/share/check_mk/livestatus
 Install Event Console           yes
 working directory of mkeventd   /var/lib/mkeventd


Proceed with installation (y/n)?

Informations supplémentaires