Changes between Version 23 and Version 24 of Doc/Monitoring/Nagios

Timestamp:

Jul 22, 2011, 5:24:39 PM (13 years ago)

Author:

/DC=org/DC=terena/DC=tcs/C=NL/O=Nikhef/CN=Ronald Starink ronalds@…

Comment:

--

Doc/Monitoring/Nagios

@@ -157 +157 @@
 Nagios servers can be used in a hierarchy, where there is 1 master server and 2 or more slave servers. The master server runs the web interface, handles notifications, performance data etc. The slave servers schedule and execute checks and submit the check results (via NSCA) to the master server. Each slave server runs (a subset of the) checks against (a subset of the) nodes. The master server receives the results for all services and all hosts.
 
-The QWG tenplates contains some generic templates for Nagios master and slave servers. However, much of the configuration is site-specific. An example setup is provided under directory `sites/example/site/nagios`. This setup must be modified to match the desired configuration of your site.
+The QWG templates contain some generic templates for Nagios master and slave servers. However, much of the configuration is site-specific. An example setup is provided under directory `sites/example/site/nagios`. This setup must be modified to match the desired configuration of your site.
 
 The generic setup consists of the following templates (under `standard/`):
@@ -170 +170 @@
  * `site/nagios/hosts/`: this directory contains the list of hosts per monitoring slave server (templates `cluster-A` and `cluster-B`) as well as a template aggregating all hosts for the master server (`all`).
  * `site/nagios/hostsgroups/`: this directory contains the list of hostgroups per monitoring slave server and an aggregating template
+ * `site/nagios/config/services/standard-templates`: list of services to be monitored; in the example cluster, there is only 1 service (load) that is monitored for all hosts. 
+ * `monitoring/nagios/services/load`: this template overrides the standard load template. It uses a variable for the service template (via variable `NAGIOS_DEFAULT_SERVICE_TEMPLATE`) to distinguish the active check (needed by slave servers) from the passive variant (used by the master). Furthermore, it includes support for an action_url to visualize performance metrics.
  * `site/nagios/nsca`: various variables for NSCA.
 
+Other templates present under the `sites/example/` directory that are not specific for the hierarchy:
+ * `site/nagios/config/apache`: example of an Apache configuration for a Nagios web server, with support for X509 certificate-based authentication via https. Users connecting to port 80 of the web server are mapped to the guest user. Because of the complexity of the Apache configuration, this template uses ncm-filecopy to get the configuration files on the server.
+ * `site/nagios/config/webinterface`: this template adds the certificate DNs for administrators to the list of people who can access the Nagios web interface via https. The administrators get access to all services, hosts, system and configuration options via the web interface.
+ * `site/nagios/site-commands`: commands that are specific to the site; that is, all commands that require non-standard 3rd party software to be installed on either the Nagios server or the nodes to be monitored. Everything means all software not contained in the rpms nagios-plugins or nagios-plugins-nrpe.