Unterschiede
Hier werden die Unterschiede zwischen zwei Versionen angezeigt.
| Beide Seiten der vorigen Revision Vorhergehende Überarbeitung Nächste Überarbeitung | Vorhergehende Überarbeitung | ||
| centos:web_c7:nagios1 [02.03.2015 13:15. ] – [IT Infrastructure Monitoring mit Nagios unter CentOS 7.x] django | centos:web_c7:nagios1 [22.07.2019 14:59. ] (aktuell) – Externe Bearbeitung 127.0.0.1 | ||
|---|---|---|---|
| Zeile 1: | Zeile 1: | ||
| - | <WRAP center round info 50%> | + | ====== IT Infrastruktur und Sytem Monitoring mit Nagios unter CentOS 7.x ====== |
| - | \\ Artikel gerade in der Bearbeitung, | + | {{: |
| - | </ | + | |
| - | + | ||
| - | + | ||
| - | ====== IT Infrastructure | + | |
| - | {{: | + | |
| Tiefergehende Informationen zu Nagios findet man auf der [[http:// | Tiefergehende Informationen zu Nagios findet man auf der [[http:// | ||
| Zeile 492: | Zeile 487: | ||
| </ | </ | ||
| - | ===== Konfiguration ===== | + | ===== Basis-Konfiguration ===== |
| ==== WEB-Server ==== | ==== WEB-Server ==== | ||
| Für die Konfiguration des Apache-Webserver liefert uns das RPM-Paket bereits eine vorgefertigte Musterdatei mit. | Für die Konfiguration des Apache-Webserver liefert uns das RPM-Paket bereits eine vorgefertigte Musterdatei mit. | ||
| Zeile 599: | Zeile 594: | ||
| $ firefox http:// | $ firefox http:// | ||
| + | {{ : | ||
| + | |||
| + | Hier geben wir nun unsere Anmeldedaten ein, die wir zuvor angelegt hatten. | ||
| + | |||
| + | {{ : | ||
| + | |||
| + | |||
| + | ===== Konfigurationsbeispiele ===== | ||
| + | Je nach Art und Umfang der zu überwachenden Systeme und Dienste nimmt der Umfang der nötigen Konfigurationsaufgaben zu. Einen kleinen Einblick gewährt z.B. nachfolgender Verzeichnisbaum in das Monitoring einer kleinen IT-Organisation. | ||
| + | |||
| + | < | ||
| + | ├── cgi.cfg | ||
| + | ├── conf.d | ||
| + | ├── nrpe.cfg | ||
| + | ├── objects | ||
| + | │ ├── commands | ||
| + | │ │ ├── check_nrpe.cfg | ||
| + | │ │ └── command_check_nrpe.cfg.test | ||
| + | │ ├── commands.cfg | ||
| + | │ ├── contacts.cfg | ||
| + | │ ├── localhost.cfg | ||
| + | │ ├── nausch.org | ||
| + | │ │ ├── commands | ||
| + | │ │ │ ├── check_sks-keyserver.cfg | ||
| + | │ │ │ ├── command_check_switch.cfg | ||
| + | │ │ │ └── command_check_webcam.cfg | ||
| + | │ │ ├── contact | ||
| + | │ │ │ ├── object_contact_django.cfg | ||
| + | │ | ||
| + | │ | ||
| + | │ | ||
| + | │ │ │ ├── object_contactgroup_admins.cfg | ||
| + | │ │ │ └── object_contact_nagiosadmin.cfg | ||
| + | │ │ ├── hostgroups | ||
| + | │ │ │ ├── dmz | ||
| + | │ │ │ │ └── hostgroups_dmz.nausch.org.cfg | ||
| + | │ │ │ └── intra | ||
| + | │ │ │ | ||
| + | │ │ │ | ||
| + | │ | ||
| + | │ │ │ | ||
| + | │ │ │ | ||
| + | │ │ ├── hosts | ||
| + | │ │ │ ├── dmz | ||
| + | │ │ │ │ ├── vml000010.cfg | ||
| + | │ | ||
| + | │ │ │ │ ├── vml000020.cfg | ||
| + | │ | ||
| + | │ │ │ │ ├── vml000030.cfg | ||
| + | │ | ||
| + | │ │ │ │ ├── vml000040.cfg | ||
| + | │ | ||
| + | │ │ │ │ ├── vml000050.cfg | ||
| + | │ | ||
| + | │ │ │ │ ├── vml000067.cfg | ||
| + | │ │ │ │ ├── vml000077.cfg | ||
| + | │ │ │ │ ├── vml000087.cfg | ||
| + | │ │ │ │ ├── vml000097.cfg | ||
| + | │ | ||
| + | │ │ │ │ └── vml000127.cfg | ||
| + | │ │ │ └── intra | ||
| + | │ │ │ | ||
| + | │ │ │ | ||
| + | │ │ │ | ||
| + | │ │ │ | ||
| + | │ │ │ | ||
| + | │ │ │ | ||
| + | │ │ │ | ||
| + | │ │ │ | ||
| + | │ │ │ | ||
| + | │ │ │ | ||
| + | │ │ │ | ||
| + | │ │ │ | ||
| + | │ | ||
| + | │ | ||
| + | │ | ||
| + | │ | ||
| + | │ | ||
| + | │ | ||
| + | │ | ||
| + | │ | ||
| + | │ │ │ | ||
| + | │ │ ├── servicegroups | ||
| + | │ │ │ ├── servicegroup_cups.cfg | ||
| + | │ │ │ ├── servicegroup_dhcp.cfg | ||
| + | │ │ │ ├── servicegroup_fhem.cfg | ||
| + | │ │ │ ├── servicegroup_firewalls.cfg | ||
| + | │ │ │ ├── servicegroup_ldap.cfg | ||
| + | │ │ │ ├── servicegroup_mail.cfg | ||
| + | │ │ │ ├── servicegroup_mysql.cfg | ||
| + | │ │ │ ├── servicegroup_proxy.cfg | ||
| + | │ │ │ ├── servicegroup_sks.cfg | ||
| + | │ │ │ ├── servicegroup_wetterstation.cfg | ||
| + | │ │ │ └── servicegroup_www.cfg | ||
| + | │ │ └── services | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ │ | ||
| + | │ ├── printer.cfg | ||
| + | │ ├── switch.cfg | ||
| + | │ ├── templates | ||
| + | │ │ ├── template_generic-contact.cfg | ||
| + | │ │ ├── template_generic-host.cfg | ||
| + | │ │ ├── template_generic-printer.cfg | ||
| + | │ │ ├── template_generic-service.cfg | ||
| + | │ │ ├── template_generic-switch.cfg | ||
| + | │ │ ├── template_hostgroup_firewalls.cfg | ||
| + | │ │ ├── template_hostgroup_linuxhosts.cfg | ||
| + | │ │ ├── template_hostgroup_virtual-linuxhosts.cfg | ||
| + | │ │ ├── template_ip-camera.cfg | ||
| + | │ │ ├── template_linux-realserver.cfg | ||
| + | │ │ ├── template_linux-virtualserver.cfg | ||
| + | │ │ ├── template_mobile-telefone.cfg | ||
| + | │ │ ├── template_network-equipment.cfg | ||
| + | │ │ ├── template_physical-telefone.cfg | ||
| + | │ │ └── template_windows-server.cfg | ||
| + | │ ├── templates.cfg | ||
| + | │ ├── timeperiods.cfg | ||
| + | │ └── windows.cfg | ||
| + | ├── passwd | ||
| + | └── private | ||
| + | └── resource.cfg | ||
| + | </ | ||
| + | |||
| + | Je nach Anforderungen kann zur Konfiguration und Verwaltung der einzelnen Objekte eine SQL-Datenbank oder auch einzelne Dateien verwendet werden. Für die IT-Landschaft bei **nausch.org** kommen entsprechende Konfigurationsdateien zum Einsatz. So können ohne großen Aufwand einzelne Objekte schnell und einfach eingestellt und angepasst werden. Auf diese einfache Konfigurationsschritte gehen wir nun anschließend bei einem System/ | ||
| + | |||
| + | ==== nagios.cfg ==== | ||
| + | Die grundlegende Konfiguration von **nagios** erfolgt mit Hilfe der Datei **nagios.cfg**. | ||
| + | # vim / | ||
| + | |||
| + | <file bash / | ||
| + | # | ||
| + | # NAGIOS.CFG - Sample Main Config File for Nagios 4.0.8 | ||
| + | # | ||
| + | # Read the documentation for more information on this configuration | ||
| + | # file. I've provided some comments here, but things may not be so | ||
| + | # clear without further explanation. | ||
| + | # | ||
| + | # | ||
| + | ############################################################################## | ||
| + | |||
| + | |||
| + | # LOG FILE | ||
| + | # This is the main log file where service and host events are logged | ||
| + | # for historical purposes. | ||
| + | # in the config file!!! | ||
| + | |||
| + | log_file=/ | ||
| + | |||
| + | |||
| + | |||
| + | # OBJECT CONFIGURATION FILE(S) | ||
| + | # These are the object configuration files in which you define hosts, | ||
| + | # host groups, contacts, contact groups, services, etc. | ||
| + | # You can split your object definitions across several config files | ||
| + | # if you wish (as shown below), or keep them all in a single config file. | ||
| + | |||
| + | # You can specify individual object config files as shown below: | ||
| + | cfg_file=/ | ||
| + | # Django : 2015-02-17 | ||
| + | # default: cfg_file=/ | ||
| + | cfg_file=/ | ||
| + | # Django : 2015-02-17 | ||
| + | # default: cfg_file=/ | ||
| + | |||
| + | # Definitions for monitoring the local (Linux) host | ||
| + | # Django : 2015-02-17 | ||
| + | # default: cfg_file=/ | ||
| + | |||
| + | # Definitions for monitoring a Windows machine | ||
| + | # | ||
| + | |||
| + | # Definitions for monitoring a router/ | ||
| + | # | ||
| + | |||
| + | # Definitions for monitoring a network printer | ||
| + | # | ||
| + | |||
| + | |||
| + | # You can also tell Nagios to process all config files (with a .cfg | ||
| + | # extension) in a particular directory by using the cfg_dir | ||
| + | # directive as shown below: | ||
| + | |||
| + | # | ||
| + | # | ||
| + | # | ||
| + | # | ||
| + | |||
| + | # Django : 2015-02-17 | ||
| + | cfg_dir=/ | ||
| + | cfg_dir=/ | ||
| + | cfg_dir=/ | ||
| + | |||
| + | cfg_dir=/ | ||
| + | |||
| + | |||
| + | |||
| + | # OBJECT CACHE FILE | ||
| + | # This option determines where object definitions are cached when | ||
| + | # Nagios starts/ | ||
| + | # this cache file (rather than looking at the object config files | ||
| + | # directly) in order to prevent inconsistencies that can occur | ||
| + | # when the config files are modified after Nagios starts. | ||
| + | |||
| + | object_cache_file=/ | ||
| + | |||
| + | |||
| + | |||
| + | # PRE-CACHED OBJECT FILE | ||
| + | # This options determines the location of the precached object file. | ||
| + | # If you run Nagios with the -p command line option, it will preprocess | ||
| + | # your object configuration file(s) and write the cached config to this | ||
| + | # file. You can then start Nagios with the -u option to have it read | ||
| + | # object definitions from this precached file, rather than the standard | ||
| + | # object configuration files (see the cfg_file and cfg_dir options above). | ||
| + | # Using a precached object file can speed up the time needed to (re)start | ||
| + | # the Nagios process if you've got a large and/or complex configuration. | ||
| + | # Read the documentation section on optimizing Nagios to find our more | ||
| + | # about how this feature works. | ||
| + | |||
| + | precached_object_file=/ | ||
| + | |||
| + | |||
| + | |||
| + | # RESOURCE FILE | ||
| + | # This is an optional resource file that contains $USERx$ macro | ||
| + | # definitions. Multiple resource files can be specified by using | ||
| + | # multiple resource_file definitions. | ||
| + | # read the contents of resource files, so information that is | ||
| + | # considered to be sensitive (usernames, passwords, etc) can be | ||
| + | # defined as macros in this file and restrictive permissions (600) | ||
| + | # can be placed on this file. | ||
| + | |||
| + | resource_file=/ | ||
| + | |||
| + | |||
| + | |||
| + | # STATUS FILE | ||
| + | # This is where the current status of all monitored services and | ||
| + | # hosts is stored. | ||
| + | # The contents of the status file are deleted every time Nagios | ||
| + | # restarts. | ||
| + | |||
| + | status_file=/ | ||
| + | |||
| + | |||
| + | |||
| + | # STATUS FILE UPDATE INTERVAL | ||
| + | # This option determines the frequency (in seconds) that | ||
| + | # Nagios will periodically dump program, host, and | ||
| + | # service status data. | ||
| + | |||
| + | status_update_interval=10 | ||
| + | |||
| + | |||
| + | |||
| + | # NAGIOS USER | ||
| + | # This determines the effective user that Nagios should run as. | ||
| + | # You can either supply a username or a UID. | ||
| + | |||
| + | nagios_user=nagios | ||
| + | |||
| + | |||
| + | |||
| + | # NAGIOS GROUP | ||
| + | # This determines the effective group that Nagios should run as. | ||
| + | # You can either supply a group name or a GID. | ||
| + | |||
| + | nagios_group=nagios | ||
| + | |||
| + | |||
| + | |||
| + | # EXTERNAL COMMAND OPTION | ||
| + | # This option allows you to specify whether or not Nagios should check | ||
| + | # for external commands (in the command file defined below). | ||
| + | # Nagios will *not* check for external commands, just to be on the | ||
| + | # cautious side. If you want to be able to use the CGI command interface | ||
| + | # you will have to enable this. | ||
| + | # Values: 0 = disable commands, 1 = enable commands | ||
| + | |||
| + | check_external_commands=1 | ||
| + | |||
| + | |||
| + | |||
| + | # EXTERNAL COMMAND FILE | ||
| + | # This is the file that Nagios checks for external command requests. | ||
| + | # It is also where the command CGI will write commands that are submitted | ||
| + | # by users, so it must be writeable by the user that the web server | ||
| + | # is running as (usually ' | ||
| + | # directory level instead of on the file, as the file is deleted every | ||
| + | # time its contents are processed. | ||
| + | |||
| + | command_file=/ | ||
| + | |||
| + | |||
| + | |||
| + | # QUERY HANDLER INTERFACE | ||
| + | # This is the socket that is created for the Query Handler interface | ||
| + | |||
| + | # | ||
| + | |||
| + | |||
| + | |||
| + | # LOCK FILE | ||
| + | # This is the lockfile that Nagios will use to store its PID number | ||
| + | # in when it is running in daemon mode. | ||
| + | |||
| + | lock_file=/ | ||
| + | |||
| + | |||
| + | |||
| + | # TEMP FILE | ||
| + | # This is a temporary file that is used as scratch space when Nagios | ||
| + | # updates the status log, cleans the comment file, etc. This file | ||
| + | # is created, used, and deleted throughout the time that Nagios is | ||
| + | # running. | ||
| + | |||
| + | temp_file=/ | ||
| + | |||
| + | |||
| + | |||
| + | # TEMP PATH | ||
| + | # This is path where Nagios can create temp files for service and | ||
| + | # host check results, etc. | ||
| + | |||
| + | temp_path=/ | ||
| + | |||
| + | |||
| + | |||
| + | # EVENT BROKER OPTIONS | ||
| + | # Controls what (if any) data gets sent to the event broker. | ||
| + | # Values: | ||
| + | # | ||
| + | # < | ||
| + | |||
| + | event_broker_options=-1 | ||
| + | |||
| + | |||
| + | |||
| + | # EVENT BROKER MODULE(S) | ||
| + | # This directive is used to specify an event broker module that should | ||
| + | # by loaded by Nagios at startup. | ||
| + | # to load more than one module. | ||
| + | # the module at startup are seperated from the module path by a space. | ||
| + | # | ||
| + | # | ||
| + | # WARNING !!! WARNING !!! WARNING !!! WARNING !!! WARNING !!! WARNING | ||
| + | # | ||
| + | # | ||
| + | # Do NOT overwrite modules while they are being used by Nagios or Nagios | ||
| + | # will crash in a fiery display of SEGFAULT glory. | ||
| + | # either in dlopen(), the kernel, and/or the filesystem. | ||
| + | # | ||
| + | # The correct/ | ||
| + | # 1. Shutdown Nagios, replace the module file, restart Nagios | ||
| + | # 2. Delete the original module file, move the new module file into place, restart Nagios | ||
| + | # | ||
| + | # Example: | ||
| + | # | ||
| + | # | ||
| + | |||
| + | # | ||
| + | # | ||
| + | |||
| + | |||
| + | |||
| + | # LOG ROTATION METHOD | ||
| + | # This is the log rotation method that Nagios should use to rotate | ||
| + | # the main log file. Values are as follows.. | ||
| + | # | ||
| + | # | ||
| + | # | ||
| + | # | ||
| + | # | ||
| + | |||
| + | log_rotation_method=d | ||
| + | |||
| + | |||
| + | |||
| + | # LOG ARCHIVE PATH | ||
| + | # This is the directory where archived (rotated) log files should be | ||
| + | # placed (assuming you've chosen to do log rotation). | ||
| + | |||
| + | log_archive_path=/ | ||
| + | |||
| + | |||
| + | |||
| + | # LOGGING OPTIONS | ||
| + | # If you want messages logged to the syslog facility, as well as the | ||
| + | # Nagios log file set this option to 1. If not, set it to 0. | ||
| + | # Django : 2015-02-17 - 1x loggen reicht! | ||
| + | # default: use_syslog=1 | ||
| + | |||
| + | use_syslog=0 | ||
| + | |||
| + | |||
| + | |||
| + | # NOTIFICATION LOGGING OPTION | ||
| + | # If you don't want notifications to be logged, set this value to 0. | ||
| + | # If notifications should be logged, set the value to 1. | ||
| + | |||
| + | log_notifications=1 | ||
| + | |||
| + | |||
| + | |||
| + | # SERVICE RETRY LOGGING OPTION | ||
| + | # If you don't want service check retries to be logged, set this value | ||
| + | # to 0. If retries should be logged, set the value to 1. | ||
| + | |||
| + | log_service_retries=1 | ||
| + | |||
| + | |||
| + | |||
| + | # HOST RETRY LOGGING OPTION | ||
| + | # If you don't want host check retries to be logged, set this value to | ||
| + | # 0. If retries should be logged, set the value to 1. | ||
| + | |||
| + | log_host_retries=1 | ||
| + | |||
| + | |||
| + | |||
| + | # EVENT HANDLER LOGGING OPTION | ||
| + | # If you don't want host and service event handlers to be logged, set | ||
| + | # this value to 0. If event handlers should be logged, set the value | ||
| + | # to 1. | ||
| + | |||
| + | log_event_handlers=1 | ||
| + | |||
| + | |||
| + | |||
| + | # INITIAL STATES LOGGING OPTION | ||
| + | # If you want Nagios to log all initial host and service states to | ||
| + | # the main log file (the first time the service or host is checked) | ||
| + | # you can enable this option by setting this value to 1. If you | ||
| + | # are not using an external application that does long term state | ||
| + | # statistics reporting, you do not need to enable this option. | ||
| + | # this case, set the value to 0. | ||
| + | |||
| + | log_initial_states=0 | ||
| + | |||
| + | |||
| + | |||
| + | # CURRENT STATES LOGGING OPTION | ||
| + | # If you don't want Nagios to log all current host and service states | ||
| + | # after log has been rotated to the main log file, you can disable this | ||
| + | # option by setting this value to 0. Default value is 1. | ||
| + | |||
| + | log_current_states=1 | ||
| + | |||
| + | |||
| + | |||
| + | # EXTERNAL COMMANDS LOGGING OPTION | ||
| + | # If you don't want Nagios to log external commands, set this value | ||
| + | # to 0. If external commands should be logged, set this value to 1. | ||
| + | # Note: This option does not include logging of passive service | ||
| + | # checks - see the option below for controlling whether or not | ||
| + | # passive checks are logged. | ||
| + | |||
| + | log_external_commands=1 | ||
| + | |||
| + | |||
| + | |||
| + | # PASSIVE CHECKS LOGGING OPTION | ||
| + | # If you don't want Nagios to log passive host and service checks, set | ||
| + | # this value to 0. If passive checks should be logged, set | ||
| + | # this value to 1. | ||
| + | |||
| + | log_passive_checks=1 | ||
| + | |||
| + | |||
| + | |||
| + | # GLOBAL HOST AND SERVICE EVENT HANDLERS | ||
| + | # These options allow you to specify a host and service event handler | ||
| + | # command that is to be run for every host or service state change. | ||
| + | # The global event handler is executed immediately prior to the event | ||
| + | # handler that you have optionally specified in each host or | ||
| + | # service definition. The command argument is the short name of a | ||
| + | # command definition that you define in your host configuration file. | ||
| + | # Read the HTML docs for more information. | ||
| + | |||
| + | # | ||
| + | # | ||
| + | |||
| + | |||
| + | |||
| + | # SERVICE INTER-CHECK DELAY METHOD | ||
| + | # This is the method that Nagios should use when initially | ||
| + | # " | ||
| + | # default is to use smart delay calculation, | ||
| + | # space all service checks out evenly to minimize CPU load. | ||
| + | # Using the dumb setting will cause all checks to be scheduled | ||
| + | # at the same time (with no delay between them)! | ||
| + | # good thing for production, but is useful when testing the | ||
| + | # parallelization functionality. | ||
| + | # | ||
| + | # | ||
| + | # | ||
| + | # | ||
| + | |||
| + | service_inter_check_delay_method=s | ||
| + | |||
| + | |||
| + | |||
| + | # MAXIMUM SERVICE CHECK SPREAD | ||
| + | # This variable determines the timeframe (in minutes) from the | ||
| + | # program start time that an initial check of all services should | ||
| + | # be completed. | ||
| + | |||
| + | max_service_check_spread=30 | ||
| + | |||
| + | |||
| + | |||
| + | # SERVICE CHECK INTERLEAVE FACTOR | ||
| + | # This variable determines how service checks are interleaved. | ||
| + | # Interleaving the service checks allows for a more even | ||
| + | # distribution of service checks and reduced load on remote | ||
| + | # hosts. | ||
| + | # of Nagios previous to 0.0.5 did service checks. | ||
| + | # value to s (smart) for automatic calculation of the interleave | ||
| + | # factor unless you have a specific reason to change it. | ||
| + | # | ||
| + | # | ||
| + | # | ||
| + | |||
| + | service_interleave_factor=s | ||
| + | |||
| + | |||
| + | |||
| + | # HOST INTER-CHECK DELAY METHOD | ||
| + | # This is the method that Nagios should use when initially | ||
| + | # " | ||
| + | # default is to use smart delay calculation, | ||
| + | # space all host checks out evenly to minimize CPU load. | ||
| + | # Using the dumb setting will cause all checks to be scheduled | ||
| + | # at the same time (with no delay between them)! | ||
| + | # | ||
| + | # | ||
| + | # | ||
| + | # | ||
| + | |||
| + | host_inter_check_delay_method=s | ||
| + | |||
| + | |||
| + | |||
| + | # MAXIMUM HOST CHECK SPREAD | ||
| + | # This variable determines the timeframe (in minutes) from the | ||
| + | # program start time that an initial check of all hosts should | ||
| + | # be completed. | ||
| + | |||
| + | max_host_check_spread=30 | ||
| + | |||
| + | |||
| + | |||
| + | # MAXIMUM CONCURRENT SERVICE CHECKS | ||
| + | # This option allows you to specify the maximum number of | ||
| + | # service checks that can be run in parallel at any given time. | ||
| + | # Specifying a value of 1 for this variable essentially prevents | ||
| + | # any service checks from being parallelized. | ||
| + | # will not restrict the number of concurrent checks that are | ||
| + | # being executed. | ||
| + | |||
| + | max_concurrent_checks=0 | ||
| + | |||
| + | |||
| + | |||
| + | # HOST AND SERVICE CHECK REAPER FREQUENCY | ||
| + | # This is the frequency (in seconds!) that Nagios will process | ||
| + | # the results of host and service checks. | ||
| + | |||
| + | check_result_reaper_frequency=10 | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | # MAX CHECK RESULT REAPER TIME | ||
| + | # This is the max amount of time (in seconds) that a single | ||
| + | # check result reaper event will be allowed to run before | ||
| + | # returning control back to Nagios so it can perform other | ||
| + | # duties. | ||
| + | |||
| + | max_check_result_reaper_time=30 | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | # CHECK RESULT PATH | ||
| + | # This is directory where Nagios stores the results of host and | ||
| + | # service checks that have not yet been processed. | ||
| + | # | ||
| + | # Note: Make sure that only one instance of Nagios has access | ||
| + | # to this directory! | ||
| + | |||
| + | check_result_path=/ | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | # MAX CHECK RESULT FILE AGE | ||
| + | # This option determines the maximum age (in seconds) which check | ||
| + | # result files are considered to be valid. | ||
| + | # threshold will be mercilessly deleted without further processing. | ||
| + | |||
| + | max_check_result_file_age=3600 | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | # CACHED HOST CHECK HORIZON | ||
| + | # This option determines the maximum amount of time (in seconds) | ||
| + | # that the state of a previous host check is considered current. | ||
| + | # Cached host states (from host checks that were performed more | ||
| + | # recently that the timeframe specified by this value) can immensely | ||
| + | # improve performance in regards to the host check logic. | ||
| + | # Too high of a value for this option may result in inaccurate host | ||
| + | # states being used by Nagios, while a lower value may result in a | ||
| + | # performance hit for host checks. | ||
| + | # check caching. | ||
| + | |||
| + | cached_host_check_horizon=15 | ||
| + | |||
| + | |||
| + | |||
| + | # CACHED SERVICE CHECK HORIZON | ||
| + | # This option determines the maximum amount of time (in seconds) | ||
| + | # that the state of a previous service check is considered current. | ||
| + | # Cached service states (from service checks that were performed more | ||
| + | # recently that the timeframe specified by this value) can immensely | ||
| + | # improve performance in regards to predictive dependency checks. | ||
| + | # Use a value of 0 to disable service check caching. | ||
| + | |||
| + | cached_service_check_horizon=15 | ||
| + | |||
| + | |||
| + | |||
| + | # ENABLE PREDICTIVE HOST DEPENDENCY CHECKS | ||
| + | # This option determines whether or not Nagios will attempt to execute | ||
| + | # checks of hosts when it predicts that future dependency logic test | ||
| + | # may be needed. | ||
| + | # host dependency logic works well. | ||
| + | # Values: | ||
| + | # 0 = Disable predictive checks | ||
| + | # 1 = Enable predictive checks (default) | ||
| + | |||
| + | enable_predictive_host_dependency_checks=1 | ||
| + | |||
| + | |||
| + | |||
| + | # ENABLE PREDICTIVE SERVICE DEPENDENCY CHECKS | ||
| + | # This option determines whether or not Nagios will attempt to execute | ||
| + | # checks of service when it predicts that future dependency logic test | ||
| + | # may be needed. | ||
| + | # service dependency logic works well. | ||
| + | # Values: | ||
| + | # 0 = Disable predictive checks | ||
| + | # 1 = Enable predictive checks (default) | ||
| + | |||
| + | enable_predictive_service_dependency_checks=1 | ||
| + | |||
| + | |||
| + | |||
| + | # SOFT STATE DEPENDENCIES | ||
| + | # This option determines whether or not Nagios will use soft state | ||
| + | # information when checking host and service dependencies. Normally | ||
| + | # Nagios will only use the latest hard host or service state when | ||
| + | # checking dependencies. If you want it to use the latest state (regardless | ||
| + | # of whether its a soft or hard state type), enable this option. | ||
| + | # Values: | ||
| + | # 0 = Don't use soft state dependencies (default) | ||
| + | # 1 = Use soft state dependencies | ||
| + | |||
| + | soft_state_dependencies=0 | ||
| + | |||
| + | |||
| + | |||
| + | # TIME CHANGE ADJUSTMENT THRESHOLDS | ||
| + | # These options determine when Nagios will react to detected changes | ||
| + | # in system time (either forward or backwards). | ||
| + | |||
| + | # | ||
| + | |||
| + | |||
| + | |||
| + | # AUTO-RESCHEDULING OPTION | ||
| + | # This option determines whether or not Nagios will attempt to | ||
| + | # automatically reschedule active host and service checks to | ||
| + | # " | ||
| + | # the monitoring server. | ||
| + | # WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE | ||
| + | # PERFORMANCE, | ||
| + | |||
| + | auto_reschedule_checks=0 | ||
| + | |||
| + | |||
| + | |||
| + | # AUTO-RESCHEDULING INTERVAL | ||
| + | # This option determines how often (in seconds) Nagios will | ||
| + | # attempt to automatically reschedule checks. | ||
| + | # has an effect if the auto_reschedule_checks option is enabled. | ||
| + | # Default is 30 seconds. | ||
| + | # WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE | ||
| + | # PERFORMANCE, | ||
| + | |||
| + | auto_rescheduling_interval=30 | ||
| + | |||
| + | |||
| + | |||
| + | # AUTO-RESCHEDULING WINDOW | ||
| + | # This option determines the " | ||
| + | # Nagios will look at when automatically rescheduling checks. | ||
| + | # Only host and service checks that occur in the next X seconds | ||
| + | # (determined by this variable) will be rescheduled. This option | ||
| + | # only has an effect if the auto_reschedule_checks option is | ||
| + | # enabled. | ||
| + | # WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE | ||
| + | # PERFORMANCE, | ||
| + | |||
| + | auto_rescheduling_window=180 | ||
| + | |||
| + | |||
| + | |||
| + | # TIMEOUT VALUES | ||
| + | # These options control how much time Nagios will allow various | ||
| + | # types of commands to execute before killing them off. Options | ||
| + | # are available for controlling maximum time allotted for | ||
| + | # service checks, host checks, event handlers, notifications, | ||
| + | # ocsp command, and performance data commands. | ||
| + | # seconds. | ||
| + | |||
| + | service_check_timeout=60 | ||
| + | host_check_timeout=30 | ||
| + | event_handler_timeout=30 | ||
| + | notification_timeout=30 | ||
| + | ocsp_timeout=5 | ||
| + | perfdata_timeout=5 | ||
| + | |||
| + | |||
| + | |||
| + | # RETAIN STATE INFORMATION | ||
| + | # This setting determines whether or not Nagios will save state | ||
| + | # information for services and hosts before it shuts down. Upon | ||
| + | # startup Nagios will reload all saved service and host state | ||
| + | # information before starting to monitor. | ||
| + | # maintaining long-term data on state statistics, etc, but will | ||
| + | # slow Nagios down a bit when it (re)starts. | ||
| + | # a one-time penalty, I think its well worth the additional | ||
| + | # startup delay. | ||
| + | |||
| + | retain_state_information=1 | ||
| + | |||
| + | |||
| + | |||
| + | # STATE RETENTION FILE | ||
| + | # This is the file that Nagios should use to store host and | ||
| + | # service state information before it shuts down. The state | ||
| + | # information in this file is also read immediately prior to | ||
| + | # starting to monitor the network when Nagios is restarted. | ||
| + | # This file is used only if the retain_state_information | ||
| + | # variable is set to 1. | ||
| + | |||
| + | state_retention_file=/ | ||
| + | |||
| + | |||
| + | |||
| + | # RETENTION DATA UPDATE INTERVAL | ||
| + | # This setting determines how often (in minutes) that Nagios | ||
| + | # will automatically save retention data during normal operation. | ||
| + | # If you set this value to 0, Nagios will not save retention | ||
| + | # data at regular interval, but it will still save retention | ||
| + | # data before shutting down or restarting. | ||
| + | # state retention, this option has no effect. | ||
| + | |||
| + | retention_update_interval=60 | ||
| + | |||
| + | |||
| + | |||
| + | # USE RETAINED PROGRAM STATE | ||
| + | # This setting determines whether or not Nagios will set | ||
| + | # program status variables based on the values saved in the | ||
| + | # retention file. If you want to use retained program status | ||
| + | # information, | ||
| + | # to 0. | ||
| + | |||
| + | use_retained_program_state=1 | ||
| + | |||
| + | |||
| + | |||
| + | # USE RETAINED SCHEDULING INFO | ||
| + | # This setting determines whether or not Nagios will retain | ||
| + | # the scheduling info (next check time) for hosts and services | ||
| + | # based on the values saved in the retention file. If you | ||
| + | # If you want to use retained scheduling info, set this | ||
| + | # value to 1. If not, set this value to 0. | ||
| + | |||
| + | use_retained_scheduling_info=1 | ||
| + | |||
| + | |||
| + | |||
| + | # RETAINED ATTRIBUTE MASKS (ADVANCED FEATURE) | ||
| + | # The following variables are used to specify specific host and | ||
| + | # service attributes that should *not* be retained by Nagios during | ||
| + | # program restarts. | ||
| + | # | ||
| + | # The values of the masks are bitwise ANDs of values specified | ||
| + | # by the " | ||
| + | # For example, if you do not want the current enabled/ | ||
| + | # of flap detection and event handlers for hosts to be retained, you | ||
| + | # would use a value of 24 for the host attribute mask... | ||
| + | # MODATTR_EVENT_HANDLER_ENABLED (8) + MODATTR_FLAP_DETECTION_ENABLED (16) = 24 | ||
| + | |||
| + | # This mask determines what host attributes are not retained | ||
| + | retained_host_attribute_mask=0 | ||
| + | |||
| + | # This mask determines what service attributes are not retained | ||
| + | retained_service_attribute_mask=0 | ||
| + | |||
| + | # These two masks determine what process attributes are not retained. | ||
| + | # There are two masks, because some process attributes have host and service | ||
| + | # options. | ||
| + | # service checks enabled. | ||
| + | retained_process_host_attribute_mask=0 | ||
| + | retained_process_service_attribute_mask=0 | ||
| + | |||
| + | # These two masks determine what contact attributes are not retained. | ||
| + | # There are two masks, because some contact attributes have host and | ||
| + | # service options. | ||
| + | # a contact, but leave service notifications enabled for them. | ||
| + | retained_contact_host_attribute_mask=0 | ||
| + | retained_contact_service_attribute_mask=0 | ||
| + | |||
| + | |||
| + | |||
| + | # INTERVAL LENGTH | ||
| + | # This is the seconds per unit interval as used in the | ||
| + | # host/ | ||
| + | # that each interval is one minute long (60 seconds). | ||
| + | # have not been tested much, so your mileage is likely to vary... | ||
| + | |||
| + | interval_length=60 | ||
| + | |||
| + | |||
| + | |||
| + | # CHECK FOR UPDATES | ||
| + | # This option determines whether Nagios will automatically check to | ||
| + | # see if new updates (releases) are available. | ||
| + | # enable this option to ensure that you stay on top of the latest critical | ||
| + | # patches to Nagios. | ||
| + | # good shape. | ||
| + | # by Nagios Enterprises from the update check is processed in accordance | ||
| + | # with our privacy policy - see http:// | ||
| + | |||
| + | check_for_updates=1 | ||
| + | |||
| + | |||
| + | |||
| + | # BARE UPDATE CHECK | ||
| + | # This option deterines what data Nagios will send to api.nagios.org when | ||
| + | # it checks for updates. | ||
| + | # current version of Nagios you have installed, as well as an indicator as | ||
| + | # to whether this was a new installation or not. Nagios Enterprises uses | ||
| + | # this data to determine the number of users running specific version of | ||
| + | # Nagios. | ||
| + | # Django : 2015-02-17 | ||
| + | # default: bare_update_check=0 | ||
| + | |||
| + | bare_update_check=1 | ||
| + | |||
| + | |||
| + | |||
| + | # AGGRESSIVE HOST CHECKING OPTION | ||
| + | # If you don't want to turn on aggressive host checking features, set | ||
| + | # this value to 0 (the default). | ||
| + | # enable the aggressive check option. | ||
| + | # on what aggressive host check is or check out the source code in | ||
| + | # base/ | ||
| + | |||
| + | use_aggressive_host_checking=0 | ||
| + | |||
| + | |||
| + | |||
| + | # SERVICE CHECK EXECUTION OPTION | ||
| + | # This determines whether or not Nagios will actively execute | ||
| + | # service checks when it initially starts. | ||
| + | # disabled, checks are not actively made, but Nagios can still | ||
| + | # receive and process passive check results that come in. Unless | ||
| + | # you're implementing redundant hosts or have a special need for | ||
| + | # disabling the execution of service checks, leave this enabled! | ||
| + | # Values: 1 = enable checks, 0 = disable checks | ||
| + | |||
| + | execute_service_checks=1 | ||
| + | |||
| + | |||
| + | |||
| + | # PASSIVE SERVICE CHECK ACCEPTANCE OPTION | ||
| + | # This determines whether or not Nagios will accept passive | ||
| + | # service checks results when it initially (re)starts. | ||
| + | # Values: 1 = accept passive checks, 0 = reject passive checks | ||
| + | |||
| + | accept_passive_service_checks=1 | ||
| + | |||
| + | |||
| + | |||
| + | # HOST CHECK EXECUTION OPTION | ||
| + | # This determines whether or not Nagios will actively execute | ||
| + | # host checks when it initially starts. | ||
| + | # disabled, checks are not actively made, but Nagios can still | ||
| + | # receive and process passive check results that come in. Unless | ||
| + | # you're implementing redundant hosts or have a special need for | ||
| + | # disabling the execution of host checks, leave this enabled! | ||
| + | # Values: 1 = enable checks, 0 = disable checks | ||
| + | |||
| + | execute_host_checks=1 | ||
| + | |||
| + | |||
| + | |||
| + | # PASSIVE HOST CHECK ACCEPTANCE OPTION | ||
| + | # This determines whether or not Nagios will accept passive | ||
| + | # host checks results when it initially (re)starts. | ||
| + | # Values: 1 = accept passive checks, 0 = reject passive checks | ||
| + | |||
| + | accept_passive_host_checks=1 | ||
| + | |||
| + | |||
| + | |||
| + | # NOTIFICATIONS OPTION | ||
| + | # This determines whether or not Nagios will sent out any host or | ||
| + | # service notifications when it is initially (re)started. | ||
| + | # Values: 1 = enable notifications, | ||
| + | |||
| + | enable_notifications=1 | ||
| + | |||
| + | |||
| + | |||
| + | # EVENT HANDLER USE OPTION | ||
| + | # This determines whether or not Nagios will run any host or | ||
| + | # service event handlers when it is initially (re)started. | ||
| + | # you're implementing redundant hosts, leave this option enabled. | ||
| + | # Values: 1 = enable event handlers, 0 = disable event handlers | ||
| + | |||
| + | enable_event_handlers=1 | ||
| + | |||
| + | |||
| + | |||
| + | # PROCESS PERFORMANCE DATA OPTION | ||
| + | # This determines whether or not Nagios will process performance | ||
| + | # data returned from service and host checks. | ||
| + | # enabled, host performance data will be processed using the | ||
| + | # host_perfdata_command (defined below) and service performance | ||
| + | # data will be processed using the service_perfdata_command (also | ||
| + | # defined below). | ||
| + | # performance data. | ||
| + | # Values: 1 = process performance data, 0 = do not process performance data | ||
| + | # Django : 2015-02-17 - Performance-Daten anlegen | ||
| + | # default: process_performance_data=0 | ||
| + | |||
| + | process_performance_data=1 | ||
| + | |||
| + | |||
| + | |||
| + | # HOST AND SERVICE PERFORMANCE DATA PROCESSING COMMANDS | ||
| + | # These commands are run after every host and service check is | ||
| + | # performed. | ||
| + | # enable_performance_data option (above) is set to 1. The command | ||
| + | # argument is the short name of a command definition that you | ||
| + | # define in your host configuration file. Read the HTML docs for | ||
| + | # more information on performance data. | ||
| + | |||
| + | # | ||
| + | # | ||
| + | |||
| + | |||
| + | |||
| + | # HOST AND SERVICE PERFORMANCE DATA FILES | ||
| + | # These files are used to store host and service performance data. | ||
| + | # Performance data is only written to these files if the | ||
| + | # enable_performance_data option (above) is set to 1. | ||
| + | |||
| + | # | ||
| + | # | ||
| + | |||
| + | |||
| + | |||
| + | # HOST AND SERVICE PERFORMANCE DATA FILE TEMPLATES | ||
| + | # These options determine what data is written (and how) to the | ||
| + | # performance data files. | ||
| + | # characters (\t for tab, \r for carriage return, \n for newline) | ||
| + | # and plain text. A newline is automatically added after each write | ||
| + | # to the performance data file. Some examples of what you can do are | ||
| + | # shown below. | ||
| + | |||
| + | # | ||
| + | # | ||
| + | |||
| + | |||
| + | |||
| + | # HOST AND SERVICE PERFORMANCE DATA FILE MODES | ||
| + | # This option determines whether or not the host and service | ||
| + | # performance data files are opened in write (" | ||
| + | # mode. If you want to use named pipes, you should use the special | ||
| + | # pipe (" | ||
| + | # likely want the defult append (" | ||
| + | |||
| + | # | ||
| + | # | ||
| + | |||
| + | |||
| + | |||
| + | # HOST AND SERVICE PERFORMANCE DATA FILE PROCESSING INTERVAL | ||
| + | # These options determine how often (in seconds) the host and service | ||
| + | # performance data files are processed using the commands defined | ||
| + | # below. | ||
| + | # processed. | ||
| + | |||
| + | # | ||
| + | # | ||
| + | |||
| + | |||
| + | |||
| + | # HOST AND SERVICE PERFORMANCE DATA FILE PROCESSING COMMANDS | ||
| + | # These commands are used to periodically process the host and | ||
| + | # service performance data files. | ||
| + | # processing occurs is determined by the options above. | ||
| + | |||
| + | # | ||
| + | # | ||
| + | |||
| + | |||
| + | |||
| + | # HOST AND SERVICE PERFORMANCE DATA PROCESS EMPTY RESULTS | ||
| + | # These options determine wether the core will process empty perfdata | ||
| + | # results or not. This is needed for distributed monitoring, and intentionally | ||
| + | # turned on by default. | ||
| + | # If you don't require empty perfdata - saving some cpu cycles | ||
| + | # on unwanted macro calculation - you can turn that off. Be careful! | ||
| + | # Values: 1 = enable, 0 = disable | ||
| + | |||
| + | # | ||
| + | # | ||
| + | |||
| + | |||
| + | # OBSESS OVER SERVICE CHECKS OPTION | ||
| + | # This determines whether or not Nagios will obsess over service | ||
| + | # checks and run the ocsp_command defined below. | ||
| + | # planning on implementing distributed monitoring, do not enable | ||
| + | # this option. | ||
| + | # implementing distributed monitoring. | ||
| + | # Values: 1 = obsess over services, 0 = do not obsess (default) | ||
| + | |||
| + | obsess_over_services=0 | ||
| + | |||
| + | |||
| + | |||
| + | # OBSESSIVE COMPULSIVE SERVICE PROCESSOR COMMAND | ||
| + | # This is the command that is run for every service check that is | ||
| + | # processed by Nagios. | ||
| + | # obsess_over_services option (above) is set to 1. The command | ||
| + | # argument is the short name of a command definition that you | ||
| + | # define in your host configuration file. Read the HTML docs for | ||
| + | # more information on implementing distributed monitoring. | ||
| + | |||
| + | # | ||
| + | |||
| + | |||
| + | |||
| + | # OBSESS OVER HOST CHECKS OPTION | ||
| + | # This determines whether or not Nagios will obsess over host | ||
| + | # checks and run the ochp_command defined below. | ||
| + | # planning on implementing distributed monitoring, do not enable | ||
| + | # this option. | ||
| + | # implementing distributed monitoring. | ||
| + | # Values: 1 = obsess over hosts, 0 = do not obsess (default) | ||
| + | |||
| + | obsess_over_hosts=0 | ||
| + | |||
| + | |||
| + | |||
| + | # OBSESSIVE COMPULSIVE HOST PROCESSOR COMMAND | ||
| + | # This is the command that is run for every host check that is | ||
| + | # processed by Nagios. | ||
| + | # obsess_over_hosts option (above) is set to 1. The command | ||
| + | # argument is the short name of a command definition that you | ||
| + | # define in your host configuration file. Read the HTML docs for | ||
| + | # more information on implementing distributed monitoring. | ||
| + | |||
| + | # | ||
| + | |||
| + | |||
| + | |||
| + | # TRANSLATE PASSIVE HOST CHECKS OPTION | ||
| + | # This determines whether or not Nagios will translate | ||
| + | # DOWN/ | ||
| + | # state for this instance of Nagios. | ||
| + | # if you have distributed or failover monitoring setup. | ||
| + | # these cases your other Nagios servers probably have a different | ||
| + | # " | ||
| + | # of hosts. | ||
| + | # is DOWN, it may actually be UNREACHABLE from the point of | ||
| + | # this Nagios instance. | ||
| + | # to translate any DOWN or UNREACHABLE host states it receives | ||
| + | # passively into the correct state from the view of this server. | ||
| + | # Values: 1 = perform translation, | ||
| + | |||
| + | translate_passive_host_checks=0 | ||
| + | |||
| + | |||
| + | |||
| + | # PASSIVE HOST CHECKS ARE SOFT OPTION | ||
| + | # This determines whether or not Nagios will treat passive host | ||
| + | # checks as being HARD or SOFT. By default, a passive host check | ||
| + | # result will put a host into a HARD state type. This can be changed | ||
| + | # by enabling this option. | ||
| + | # Values: 0 = passive checks are HARD, 1 = passive checks are SOFT | ||
| + | |||
| + | passive_host_checks_are_soft=0 | ||
| + | |||
| + | |||
| + | |||
| + | # ORPHANED HOST/ | ||
| + | # These options determine whether or not Nagios will periodically | ||
| + | # check for orphaned host service checks. | ||
| + | # not rescheduled until the results of their previous execution | ||
| + | # instance are processed, there exists a possibility that some | ||
| + | # checks may never get rescheduled. | ||
| + | # host checks, although the exact scheduling details differ a bit | ||
| + | # from service checks. | ||
| + | # problem and should not happen under normal circumstances. | ||
| + | # If you have problems with service checks never getting | ||
| + | # rescheduled, | ||
| + | # Values: 1 = enable checks, 0 = disable checks | ||
| + | |||
| + | check_for_orphaned_services=1 | ||
| + | check_for_orphaned_hosts=1 | ||
| + | |||
| + | |||
| + | |||
| + | # SERVICE FRESHNESS CHECK OPTION | ||
| + | # This option determines whether or not Nagios will periodically | ||
| + | # check the " | ||
| + | # is useful for ensuring passive checks are received in a timely | ||
| + | # manner. | ||
| + | # Values: 1 = enabled freshness checking, 0 = disable freshness checking | ||
| + | |||
| + | check_service_freshness=1 | ||
| + | |||
| + | |||
| + | |||
| + | # SERVICE FRESHNESS CHECK INTERVAL | ||
| + | # This setting determines how often (in seconds) Nagios will | ||
| + | # check the " | ||
| + | # disabled service freshness checking, this option has no effect. | ||
| + | |||
| + | service_freshness_check_interval=60 | ||
| + | |||
| + | |||
| + | |||
| + | # SERVICE CHECK TIMEOUT STATE | ||
| + | # This setting determines the state Nagios will report when a | ||
| + | # service check times out - that is does not respond within | ||
| + | # service_check_timeout seconds. | ||
| + | # machine is running at too high a load and you do not want | ||
| + | # to consider a failed service check to be critical (the default). | ||
| + | # Valid settings are: | ||
| + | # c - Critical (default) | ||
| + | # u - Unknown | ||
| + | # w - Warning | ||
| + | # o - OK | ||
| + | |||
| + | service_check_timeout_state=c | ||
| + | |||
| + | |||
| + | |||
| + | # HOST FRESHNESS CHECK OPTION | ||
| + | # This option determines whether or not Nagios will periodically | ||
| + | # check the " | ||
| + | # is useful for ensuring passive checks are received in a timely | ||
| + | # manner. | ||
| + | # Values: 1 = enabled freshness checking, 0 = disable freshness checking | ||
| + | |||
| + | check_host_freshness=0 | ||
| + | |||
| + | |||
| + | |||
| + | # HOST FRESHNESS CHECK INTERVAL | ||
| + | # This setting determines how often (in seconds) Nagios will | ||
| + | # check the " | ||
| + | # disabled host freshness checking, this option has no effect. | ||
| + | |||
| + | host_freshness_check_interval=60 | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | # ADDITIONAL FRESHNESS THRESHOLD LATENCY | ||
| + | # This setting determines the number of seconds that Nagios | ||
| + | # will add to any host and service freshness thresholds that | ||
| + | # it calculates (those not explicitly specified by the user). | ||
| + | |||
| + | additional_freshness_latency=15 | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | # FLAP DETECTION OPTION | ||
| + | # This option determines whether or not Nagios will try | ||
| + | # and detect hosts and services that are " | ||
| + | # Flapping occurs when a host or service changes between | ||
| + | # states too frequently. | ||
| + | # host or service is flapping, it will temporarily suppress | ||
| + | # notifications for that host/ | ||
| + | # flapping. | ||
| + | # the HTML documentation before enabling this feature! | ||
| + | # Values: 1 = enable flap detection | ||
| + | # 0 = disable flap detection (default) | ||
| + | |||
| + | enable_flap_detection=1 | ||
| + | |||
| + | |||
| + | |||
| + | # FLAP DETECTION THRESHOLDS FOR HOSTS AND SERVICES | ||
| + | # Read the HTML documentation on flap detection for | ||
| + | # an explanation of what this option does. This option | ||
| + | # has no effect if flap detection is disabled. | ||
| + | |||
| + | low_service_flap_threshold=5.0 | ||
| + | high_service_flap_threshold=20.0 | ||
| + | low_host_flap_threshold=5.0 | ||
| + | high_host_flap_threshold=20.0 | ||
| + | |||
| + | |||
| + | |||
| + | # DATE FORMAT OPTION | ||
| + | # This option determines how short dates are displayed. Valid options | ||
| + | # include: | ||
| + | # | ||
| + | # | ||
| + | # | ||
| + | # | ||
| + | # | ||
| + | # Django : 2015-02-17 | ||
| + | # default: date_format=us | ||
| + | |||
| + | date_format=euro | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | # TIMEZONE OFFSET | ||
| + | # This option is used to override the default timezone that this | ||
| + | # instance of Nagios runs in. If not specified, Nagios will use | ||
| + | # the system configured timezone. | ||
| + | # | ||
| + | # NOTE: In order to display the correct timezone in the CGIs, you | ||
| + | # will also need to alter the Apache directives for the CGI path | ||
| + | # to include your timezone. | ||
| + | # | ||
| + | # < | ||
| + | # SetEnv TZ " | ||
| + | # ... | ||
| + | # </ | ||
| + | |||
| + | # | ||
| + | # | ||
| + | |||
| + | # Django : 2015-02-17 | ||
| + | # default: unset | ||
| + | use_timezone=Europe/ | ||
| + | |||
| + | |||
| + | # ILLEGAL OBJECT NAME CHARACTERS | ||
| + | # This option allows you to specify illegal characters that cannot | ||
| + | # be used in host names, service descriptions, | ||
| + | # object types. | ||
| + | |||
| + | illegal_object_name_chars=`~!$%^& | ||
| + | |||
| + | |||
| + | |||
| + | # ILLEGAL MACRO OUTPUT CHARACTERS | ||
| + | # This option allows you to specify illegal characters that are | ||
| + | # stripped from macros before being used in notifications, | ||
| + | # handlers, etc. This DOES NOT affect macros used in service or | ||
| + | # host check commands. | ||
| + | # The following macros are stripped of the characters you specify: | ||
| + | # | ||
| + | # | ||
| + | # | ||
| + | # | ||
| + | # | ||
| + | # | ||
| + | # | ||
| + | # | ||
| + | |||
| + | illegal_macro_output_chars=`~$& | ||
| + | |||
| + | |||
| + | |||
| + | # REGULAR EXPRESSION MATCHING | ||
| + | # This option controls whether or not regular expression matching | ||
| + | # takes place in the object config files. | ||
| + | # matching is used to match host, hostgroup, service, and service | ||
| + | # group names/ | ||
| + | # Values: 1 = enable regexp matching, 0 = disable regexp matching | ||
| + | |||
| + | use_regexp_matching=0 | ||
| + | |||
| + | |||
| + | |||
| + | # " | ||
| + | # This option controls whether or not " | ||
| + | # matching takes place in the object config files. | ||
| + | # only has an effect if regular expression matching is enabled | ||
| + | # (see above). | ||
| + | # matching only occurs if a string contains wildcard characters | ||
| + | # (* and ?). If the option is ENABLED, regexp matching occurs | ||
| + | # all the time (which can be annoying). | ||
| + | # Values: 1 = enable true matching, 0 = disable true matching | ||
| + | |||
| + | use_true_regexp_matching=0 | ||
| + | |||
| + | |||
| + | |||
| + | # ADMINISTRATOR EMAIL/PAGER ADDRESSES | ||
| + | # The email and pager address of a global administrator (likely you). | ||
| + | # Nagios never uses these values itself, but you can access them by | ||
| + | # using the $ADMINEMAIL$ and $ADMINPAGER$ macros in your notification | ||
| + | # commands. | ||
| + | |||
| + | # Django : 2015-02-17 | ||
| + | # default: admin_email=nagios@localhost | ||
| + | # admin_pager=pagenagios@localhost | ||
| + | # | ||
| + | # | ||
| + | admin_email="" | ||
| + | admin_pager="" | ||
| + | |||
| + | |||
| + | |||
| + | # DAEMON CORE DUMP OPTION | ||
| + | # This option determines whether or not Nagios is allowed to create | ||
| + | # a core dump when it runs as a daemon. | ||
| + | # considered bad form to allow this, but it may be useful for | ||
| + | # debugging purposes. | ||
| + | # a core file will be produced, but that's just life... | ||
| + | # Values: 1 - Allow core dumps | ||
| + | # 0 - Do not allow core dumps (default) | ||
| + | |||
| + | daemon_dumps_core=0 | ||
| + | |||
| + | |||
| + | |||
| + | # LARGE INSTALLATION TWEAKS OPTION | ||
| + | # This option determines whether or not Nagios will take some shortcuts | ||
| + | # which can save on memory and CPU usage in large Nagios installations. | ||
| + | # Read the documentation for more information on the benefits/ | ||
| + | # of enabling this option. | ||
| + | # Values: 1 - Enabled tweaks | ||
| + | # 0 - Disable tweaks (default) | ||
| + | |||
| + | use_large_installation_tweaks=0 | ||
| + | |||
| + | |||
| + | |||
| + | # ENABLE ENVIRONMENT MACROS | ||
| + | # This option determines whether or not Nagios will make all standard | ||
| + | # macros available as environment variables when host/ | ||
| + | # and system commands (event handlers, notifications, | ||
| + | # executed. | ||
| + | # Enabling this is a very bad idea for anything but very small setups, | ||
| + | # as it means plugins, notification scripts and eventhandlers may run | ||
| + | # out of environment space. It will also cause a significant increase | ||
| + | # in CPU- and memory usage and drastically reduce the number of checks | ||
| + | # you can run. | ||
| + | # Values: 1 - Enable environment variable macros | ||
| + | # 0 - Disable environment variable macros (default) | ||
| + | |||
| + | enable_environment_macros=0 | ||
| + | |||
| + | |||
| + | |||
| + | # CHILD PROCESS MEMORY OPTION | ||
| + | # This option determines whether or not Nagios will free memory in | ||
| + | # child processes (processed used to execute system commands and host/ | ||
| + | # service checks). | ||
| + | # program defaults. | ||
| + | # Value: 1 - Free memory in child processes | ||
| + | # 0 - Do not free memory in child processes | ||
| + | |||
| + | # | ||
| + | |||
| + | |||
| + | |||
| + | # CHILD PROCESS FORKING BEHAVIOR | ||
| + | # This option determines how Nagios will fork child processes | ||
| + | # (used to execute system commands and host/ | ||
| + | # child processes are fork()ed twice, which provides a very high level | ||
| + | # of isolation from problems. | ||
| + | # save a great deal on CPU usage (in large installs), so you might | ||
| + | # want to consider using this. If you specify a value here, it will | ||
| + | # program defaults. | ||
| + | # Value: 1 - Child processes fork() twice | ||
| + | # 0 - Child processes fork() just once | ||
| + | |||
| + | # | ||
| + | |||
| + | |||
| + | |||
| + | # DEBUG LEVEL | ||
| + | # This option determines how much (if any) debugging information will | ||
| + | # be written to the debug file. OR values together to log multiple | ||
| + | # types of information. | ||
| + | # Values: | ||
| + | # -1 = Everything | ||
| + | # 0 = Nothing | ||
| + | # 1 = Functions | ||
| + | # 2 = Configuration | ||
| + | # 4 = Process information | ||
| + | # 8 = Scheduled events | ||
| + | # 16 = Host/ | ||
| + | # 32 = Notifications | ||
| + | # 64 = Event broker | ||
| + | # 128 = External commands | ||
| + | # 256 = Commands | ||
| + | # 512 = Scheduled downtime | ||
| + | # 1024 = Comments | ||
| + | # 2048 = Macros | ||
| + | |||
| + | debug_level=0 | ||
| + | |||
| + | |||
| + | |||
| + | # DEBUG VERBOSITY | ||
| + | # This option determines how verbose the debug log out will be. | ||
| + | # Values: 0 = Brief output | ||
| + | # 1 = More detailed | ||
| + | # 2 = Very detailed | ||
| + | |||
| + | debug_verbosity=1 | ||
| + | |||
| + | |||
| + | |||
| + | # DEBUG FILE | ||
| + | # This option determines where Nagios should write debugging information. | ||
| + | |||
| + | debug_file=/ | ||
| + | |||
| + | |||
| + | |||
| + | # MAX DEBUG FILE SIZE | ||
| + | # This option determines the maximum size (in bytes) of the debug file. If | ||
| + | # the file grows larger than this size, it will be renamed with a .old | ||
| + | # extension. | ||
| + | # automatically be deleted. | ||
| + | # get out of control when debugging Nagios. | ||
| + | |||
| + | max_debug_file_size=1000000 | ||
| + | |||
| + | |||
| + | |||
| + | # Should we allow hostgroups to have no hosts, we default this to off since | ||
| + | # that was the old behavior | ||
| + | |||
| + | allow_empty_hostgroup_assignment=0 | ||
| + | |||
| + | |||
| + | |||
| + | # Normally worker count is dynamically allocated based on 1.5 * number of cpu's | ||
| + | # with a minimum of 4 workers. | ||
| + | |||
| + | # | ||
| + | |||
| + | |||
| + | |||
| + | # EXPERIMENTAL load controlling options | ||
| + | # To get current defaults based on your system issue a command to | ||
| + | # the query handler. Please note that this is an experimental feature | ||
| + | # and not meant for production use. Used incorrectly it can induce | ||
| + | # enormous latency. | ||
| + | # #core loadctl | ||
| + | # | ||
| + | # | ||
| + | # | ||
| + | # | ||
| + | # | ||
| + | # | ||
| + | # | ||
| + | # NOTE: The backoff_limit and rampup_limit are NOT used by anything currently, | ||
| + | # so if your system is under load nothing will actively modify the jobs | ||
| + | # even if you have these options enabled, they are for external | ||
| + | # | ||
| + | # | ||
| + | # WILL affect your system | ||
| + | # | ||
| + | </ | ||
| + | |||
| + | ==== Definition CONTACT ==== | ||
| + | Damit unser Admin **// | ||
| + | # vim / | ||
| + | |||
| + | <file bash / | ||
| + | contact_name | ||
| + | alias | ||
| + | use | ||
| + | email | ||
| + | address2 | ||
| + | can_submit_commands | ||
| + | } | ||
| + | </ | ||
| + | |||
| + | |||
| + | ==== Definition HOST ==== | ||
| + | Um einen einzelnen Server zu monitoren legen wir uns eine Datei im Verzeichnis // | ||
| + | # vim / | ||
| + | <file bash / | ||
| + | use | ||
| + | host_name | ||
| + | alias | ||
| + | address | ||
| + | notes_url | ||
| + | } | ||
| + | |||
| + | </ | ||
| + | |||
| + | |||
| + | ==== Definition HOST-GRUPPE ==== | ||
| + | Einzelne Server gruppieren wir entsprechend ihrem Einsatzzweck bzw. ihres Aufstellungsortes. | ||
| + | # vim / | ||
| + | |||
| + | <file bash / | ||
| + | # Alle Hosts der DMZ | ||
| + | |||
| + | define hostgroup { | ||
| + | hostgroup_name | ||
| + | alias DMZ | ||
| + | members | ||
| + | } | ||
| + | </ | ||
| + | |||
| + | ==== Definition NRPE ==== | ||
| + | Damit unser Nagios-Server auf dem Remote-System auch entsprechende Checks anstoßen kann, bedarf es der Konfiguration des **[[http:// | ||
| + | # vim / | ||
| + | |||
| + | <file bash / | ||
| + | # Sample NRPE Config File | ||
| + | # Written by: Ethan Galstad (nagios@nagios.org) | ||
| + | # | ||
| + | # Last Modified: 11-23-2007 | ||
| + | # | ||
| + | # NOTES: | ||
| + | # This is a sample configuration file for the NRPE daemon. | ||
| + | # located on the remote host that is running the NRPE daemon, not the host | ||
| + | # from which the check_nrpe client is being executed. | ||
| + | ############################################################################# | ||
| + | |||
| + | |||
| + | # LOG FACILITY | ||
| + | # The syslog facility that should be used for logging purposes. | ||
| + | |||
| + | log_facility=daemon | ||
| + | |||
| + | |||
| + | |||
| + | # PID FILE | ||
| + | # The name of the file in which the NRPE daemon should write it's process ID | ||
| + | # number. | ||
| + | # user and is running in standalone mode. | ||
| + | |||
| + | pid_file=/ | ||
| + | |||
| + | |||
| + | |||
| + | # PORT NUMBER | ||
| + | # Port number we should wait for connections on. | ||
| + | # NOTE: This must be a non-priviledged port (i.e. > 1024). | ||
| + | # NOTE: This option is ignored if NRPE is running under either inetd or xinetd | ||
| + | |||
| + | server_port=5666 | ||
| + | |||
| + | |||
| + | |||
| + | # SERVER ADDRESS | ||
| + | # Address that nrpe should bind to in case there are more than one interface | ||
| + | # and you do not want nrpe to bind on all interfaces. | ||
| + | # NOTE: This option is ignored if NRPE is running under either inetd or xinetd | ||
| + | |||
| + | # Django : 2015-01-27 | ||
| + | # default: # | ||
| + | server_address=10.0.0.67 | ||
| + | |||
| + | |||
| + | # NRPE USER | ||
| + | # This determines the effective user that the NRPE daemon should run as. | ||
| + | # You can either supply a username or a UID. | ||
| + | # | ||
| + | # NOTE: This option is ignored if NRPE is running under either inetd or xinetd | ||
| + | |||
| + | nrpe_user=nrpe | ||
| + | |||
| + | |||
| + | |||
| + | # NRPE GROUP | ||
| + | # This determines the effective group that the NRPE daemon should run as. | ||
| + | # You can either supply a group name or a GID. | ||
| + | # | ||
| + | # NOTE: This option is ignored if NRPE is running under either inetd or xinetd | ||
| + | |||
| + | nrpe_group=nrpe | ||
| + | |||
| + | |||
| + | |||
| + | # ALLOWED HOST ADDRESSES | ||
| + | # This is an optional comma-delimited list of IP address or hostnames | ||
| + | # that are allowed to talk to the NRPE daemon. Network addresses with a bit mask | ||
| + | # (i.e. 192.168.1.0/ | ||
| + | # supported. | ||
| + | # | ||
| + | # Note: The daemon only does rudimentary checking of the client' | ||
| + | # address. | ||
| + | # file to allow only the specified host to connect to the port | ||
| + | # you are running this daemon on. | ||
| + | # | ||
| + | # NOTE: This option is ignored if NRPE is running under either inetd or xinetd | ||
| + | |||
| + | # Django : 2015-01-27 | ||
| + | # default: allowed_hosts=127.0.0.1 | ||
| + | allowed_hosts=10.0.0.127 | ||
| + | |||
| + | # COMMAND ARGUMENT PROCESSING | ||
| + | # This option determines whether or not the NRPE daemon will allow clients | ||
| + | # to specify arguments to commands that are executed. | ||
| + | # if the daemon was configured with the --enable-command-args configure script | ||
| + | # option. | ||
| + | # | ||
| + | # *** ENABLING THIS OPTION IS A SECURITY RISK! *** | ||
| + | # Read the SECURITY file for information on some of the security implications | ||
| + | # of enabling this variable. | ||
| + | # | ||
| + | # Values: 0=do not allow arguments, 1=allow command arguments | ||
| + | |||
| + | dont_blame_nrpe=0 | ||
| + | |||
| + | |||
| + | |||
| + | # BASH COMMAND SUBTITUTION | ||
| + | # This option determines whether or not the NRPE daemon will allow clients | ||
| + | # to specify arguments that contain bash command substitutions of the form | ||
| + | # $(...). | ||
| + | # the --enable-command-args and --enable-bash-command-substitution configure | ||
| + | # script options. | ||
| + | # | ||
| + | # *** ENABLING THIS OPTION IS A HIGH SECURITY RISK! *** | ||
| + | # Read the SECURITY file for information on some of the security implications | ||
| + | # of enabling this variable. | ||
| + | # | ||
| + | # Values: 0=do not allow bash command substitutions, | ||
| + | # | ||
| + | |||
| + | allow_bash_command_substitution=0 | ||
| + | |||
| + | |||
| + | |||
| + | # COMMAND PREFIX | ||
| + | # This option allows you to prefix all commands with a user-defined string. | ||
| + | # A space is automatically added between the specified prefix string and the | ||
| + | # command line from the command definition. | ||
| + | # | ||
| + | # *** THIS EXAMPLE MAY POSE A POTENTIAL SECURITY RISK, SO USE WITH CAUTION! *** | ||
| + | # Usage scenario: | ||
| + | # Execute restricted commmands using sudo. For this to work, you need to add | ||
| + | # the nagios user to your / | ||
| + | # execution of the plugins from might be: | ||
| + | # | ||
| + | # nagios | ||
| + | # | ||
| + | # This lets the nagios user run all commands in that directory (and only them) | ||
| + | # without asking for a password. | ||
| + | # random users write access to that directory or its contents! | ||
| + | |||
| + | # command_prefix=/ | ||
| + | |||
| + | |||
| + | |||
| + | # DEBUGGING OPTION | ||
| + | # This option determines whether or not debugging messages are logged to the | ||
| + | # syslog facility. | ||
| + | # Values: 0=debugging off, 1=debugging on | ||
| + | |||
| + | debug=0 | ||
| + | |||
| + | |||
| + | |||
| + | # COMMAND TIMEOUT | ||
| + | # This specifies the maximum number of seconds that the NRPE daemon will | ||
| + | # allow plugins to finish executing before killing them off. | ||
| + | |||
| + | command_timeout=60 | ||
| + | |||
| + | |||
| + | |||
| + | # CONNECTION TIMEOUT | ||
| + | # This specifies the maximum number of seconds that the NRPE daemon will | ||
| + | # wait for a connection to be established before exiting. This is sometimes | ||
| + | # seen where a network problem stops the SSL being established even though | ||
| + | # all network sessions are connected. This causes the nrpe daemons to | ||
| + | # accumulate, eating system resources. Do not set this too low. | ||
| + | |||
| + | connection_timeout=300 | ||
| + | |||
| + | |||
| + | |||
| + | # WEEK RANDOM SEED OPTION | ||
| + | # This directive allows you to use SSL even if your system does not have | ||
| + | # a /dev/random or / | ||
| + | # were not applied). The random number generator will be seeded from a file | ||
| + | # which is either a file pointed to by the environment valiable $RANDFILE | ||
| + | # or $HOME/.rnd. If neither exists, the pseudo random number generator will | ||
| + | # be initialized and a warning will be issued. | ||
| + | # Values: 0=only seed from / | ||
| + | |||
| + | # | ||
| + | |||
| + | |||
| + | |||
| + | # INCLUDE CONFIG FILE | ||
| + | # This directive allows you to include definitions from an external config file. | ||
| + | |||
| + | # | ||
| + | |||
| + | |||
| + | |||
| + | # COMMAND DEFINITIONS | ||
| + | # Command definitions that this daemon will run. Definitions | ||
| + | # are in the following format: | ||
| + | # | ||
| + | # command[< | ||
| + | # | ||
| + | # When the daemon receives a request to return the results of < | ||
| + | # it will execute the command specified by the < | ||
| + | # | ||
| + | # Unlike Nagios, the command line cannot contain macros - it must be | ||
| + | # typed exactly as it should be executed. | ||
| + | # | ||
| + | # Note: Any plugins that are used in the command lines must reside | ||
| + | # on the machine that this daemon is running on! The examples below | ||
| + | # assume that you have plugins installed in a / | ||
| + | # directory. | ||
| + | # to match the argument format the plugins expect. | ||
| + | # examples only! | ||
| + | |||
| + | |||
| + | # The following examples use hardcoded command arguments... | ||
| + | |||
| + | # Django : 2015-01-27 | ||
| + | # allgemeiner Host-Teil | ||
| + | command[check_tcp_5666]=/ | ||
| + | command[check_users]=/ | ||
| + | command[check_load]=/ | ||
| + | command[check_fs_boot]=/ | ||
| + | command[check_fs_root]=/ | ||
| + | command[check_fs_varlog]=/ | ||
| + | command[check_fs_ramdisk_sudo]=/ | ||
| + | command[check_swap]=/ | ||
| + | |||
| + | command[check_updates]=/ | ||
| + | command[check_zombie_procs]=/ | ||
| + | command[check_total_procs]=/ | ||
| + | command[check_running_iptables]=/ | ||
| + | command[check_if_traffic_eth0]=/ | ||
| + | command[check_crond]=/ | ||
| + | |||
| + | # Mailserver spezifische Test | ||
| + | command[check_running_postfix]=/ | ||
| + | command[check_running_amavisd]=/ | ||
| + | command[check_running_clamd]=/ | ||
| + | command[check_clamav]=/ | ||
| + | |||
| + | command[check_tcp_25]=/ | ||
| + | command[check_tcp_783]=/ | ||
| + | command[check_tcp_8899]=/ | ||
| + | command[check_tcp_9998]=/ | ||
| + | command[check_tcp_10024]=/ | ||
| + | |||
| + | command[check_sending_mail_10024]=/ | ||
| + | command[check_sending_mail_10025]=/ | ||
| + | |||
| + | |||
| + | # The following examples allow user-supplied arguments and can | ||
| + | # only be used if the NRPE daemon was compiled with support for | ||
| + | # command arguments *AND* the dont_blame_nrpe directive in this | ||
| + | # config file is set to ' | ||
| + | # make sure you read the SECURITY file before doing this. | ||
| + | |||
| + | # | ||
| + | # | ||
| + | # | ||
| + | # | ||
| + | |||
| + | |||
| + | |||
| + | # INCLUDE CONFIG DIRECTORY | ||
| + | # This directive allows you to include definitions from config files (with a | ||
| + | # .cfg extension) in one or more directories (with recursion). | ||
| + | |||
| + | include_dir=/ | ||
| + | </ | ||
| + | |||
| + | ==== Definition SERVICE ==== | ||
| + | Für jeden Check benötigen wir nun noch eine Definitionsdatei im Verzeichnis //** / | ||
| + | Zur Überwachung des Netzwerktraffics auf dem Netzwerkinterface **eth0** legen wir uns eine zugehörige Datei an. | ||
| + | # vim / | ||
| + | |||
| + | <file bash / | ||
| + | use | ||
| + | hostgroup_name | ||
| + | # | ||
| + | service_description | ||
| + | check_command | ||
| + | } | ||
| + | </ | ||
| + | |||
| + | ==== Definition SERVICEGROUP ==== | ||
| + | Betrachtet man einen Dienst wie z.B. **eMail** so wird man sehr schnell feststellen, | ||
| + | # vim / | ||
| + | |||
| + | <file bash / | ||
| + | servicegroup_name | ||
| + | alias | ||
| + | } | ||
| + | </ | ||
| + | |||
| + | Damit nun bei den einzelnen Services die zugehörige Servicegroup herangezogen wird, tragen wir diese in der Definitionsdatei des Services ein. Das nachfolgende Beispiel zeigt exemplarisch die Überwachungskonfigurationsdatei des Postfix-Daemon. | ||
| + | # vim / | ||
| + | |||
| + | <file bash / | ||
| + | use | ||
| + | host_name | ||
| + | # | ||
| + | servicegroups | ||
| + | service_description | ||
| + | check_command | ||
| + | } | ||
| + | </ | ||
| + | |||
| + | In der Servicegruppe **mail** wird also geprüft ob auf den drei Servern der Postfix-Daemon läuft. | ||
| + | |||
| + | ==== Konfigurations-Überprüfung ==== | ||
| + | Bevor wir nach einer Änderung oder Erweiterung unserer Server- und Service-Überwachung mit einem **reload** des **Nagios-// | ||
| + | # nagios -pv / | ||
| + | |||
| + | < | ||
| + | Copyright (c) 2009-present Nagios Core Development Team and Community Contributors | ||
| + | Copyright (c) 1999-2009 Ethan Galstad | ||
| + | Last Modified: 08-12-2014 | ||
| + | License: GPL | ||
| + | |||
| + | Website: http:// | ||
| + | Reading configuration data... | ||
| + | Read main config file okay... | ||
| + | Read object config files okay... | ||
| + | |||
| + | Running pre-flight check on configuration data... | ||
| + | |||
| + | Checking objects... | ||
| + | Checked 522 services. | ||
| + | Checked 26 hosts. | ||
| + | Checked 6 host groups. | ||
| + | Checked 16 service groups. | ||
| + | Checked 6 contacts. | ||
| + | Checked 2 contact groups. | ||
| + | Checked 28 commands. | ||
| + | Checked 5 time periods. | ||
| + | Checked 0 host escalations. | ||
| + | Checked 0 service escalations. | ||
| + | Checking for circular paths... | ||
| + | Checked 26 hosts | ||
| + | Checked 0 service dependencies | ||
| + | Checked 0 host dependencies | ||
| + | Checked 5 timeperiods | ||
| + | Checking global event handlers... | ||
| + | Checking obsessive compulsive processor commands... | ||
| + | Checking misc settings... | ||
| + | |||
| + | Total Warnings: 0 | ||
| + | Total Errors: | ||
| + | |||
| + | Things look okay - No serious problems were detected during the pre-flight check | ||
| + | Object precache file created: | ||
| + | / | ||
| + | </ | ||
| + | |||
| + | Da alles in Ordnung ist können wir nun ohne großen Bedenken den Reload des nagios-Daemon durchführen. | ||
| + | # systemctl reload nagios | ||
| + | |||
| + | Tippfaule Admins fassen die Überprüfen und den Reload in einen Aufruf zusammen, indem dieser durch **&& | ||
| + | # nagios -pv / | ||
| + | |||
| + | Trat ein Fehler auf, können wir diesen erst beseitigen und den Daemon anschließend erneut testen und reloaden. Rufen wir anschließend das Nagios-Webfrontend erneut auf, werden unsere Server und Dienste entsprechend zur Anzeige gebracht, in dem man mit einem Klick auf die zugehörigen Menüpunkt am linken Bildschirmrand klickt. | ||
| + | {{ : | ||
| + | ====== Links ====== | ||
| + | * **[[centos: | ||
| + | * **[[wiki: | ||
| + | * **[[http:// | ||
django