Changes between Version 13 and Version 14 of Doc/Monitoring/Nagios
- Timestamp:
- Jul 17, 2008, 3:45:01 PM (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Doc/Monitoring/Nagios
v13 v14 7 7 = Configuring the Nagios server = 8 8 9 The configuration of a Nagios server is done in a set of ''standard'' templates, in the [source:templates/trunk/standard/monitoring/nagios ''monitoring/nagios''] namespace. 9 The configuration of a Nagios server is done in a set of ''standard'' templates, in the [source:templates/trunk/standard/monitoring/nagios ''monitoring/nagios''] namespace. Also, sensors are provided for many of the plug-ins described on the [http://www.gridpp.ac.uk/wiki/Nagios_Plugins GridPP wiki]. An [source:templates/trunk/clusters/example-3.1/profiles/nagios-server.example.org.tpl example Nagios server template] is included in the QWG distribution. 10 10 11 Also, sensors are provided for many of the plug-ins described in [http://www.gridpp.ac.uk/wiki/Nagios_Plugins GridPP's wiki] 11 In order to configure a basic nagios server, simply include the template [source:templates/trunk/standard/monitoring/nagios/config monitoring/nagios/config] in the server's template. This will automatically generate a Nagios configuration that monitors all Quattor-managed machines. 12 13 == Monitoring grid services == 14 Preliminary work has been done to integrate monitoring of grid services according to the EGEE model (described at https://twiki.cern.ch/twiki/bin/view/LCG/GridMonitoringNcg). 15 16 = Customising your configuration = 12 17 13 18 == What is monitored == 14 19 15 In principle, all hosts present on `DB_MACHINE` are expected to be monitored and are added to Nagios configuration. This is done with the variables `HOSTSLIST`, which is automatically derived from `DB_MACHINE`. Additional hosts can be specified withthe variable `NAGIOS_EXTRA_HOSTS`.20 In principle, all hosts present in the `DB_MACHINE` database are expected to be monitored and are added to Nagios configuration. (This is done via the variable `HOSTSLIST`, which is automatically derived from `DB_MACHINE`.) If you want to monitor additional hosts that are not Quattor-managed, they can be specified in the variable `NAGIOS_EXTRA_HOSTS`. 16 21 17 Currently, all hosts are considered to havethe same settings. Finer-grained settings (for instance, separate hosts to be monitored on working and non-working hours) are yet to be done.22 Currently, all hosts are given the same settings. Finer-grained settings (for instance, separate hosts to be monitored on working and non-working hours) are yet to be done. 18 23 19 24 == Hardware-related monitoring == 20 25 21 The variable `HW_LISTINGS` is somewhat the "inverse" from `DB_MACHINE`: it is a structure with fields related to some hardware attribute and whose values are the lists of nodes with such attribute. For instance, `HW_LISTINGS["per_cpu"]["_4"]` is the list of nodes with 4 CPU cores, should that be 4 old Pentium or a single Barcelona chip. See [#Variable-index here] for the full description of each variable.26 The variable `HW_LISTINGS` is essentially the inverse of `DB_MACHINE`: it is a structure with fields related to some hardware attribute and whose values are the lists of nodes with such attribute. For instance, `HW_LISTINGS["per_cpu"]["_4"]` is the list of nodes with 4 CPU cores, whether 4 single-code Pentiums or a single quad-core Barcelona chip. See [#Variable-index here] for the full description of each variable. 22 27 23 28 == Specifying commands ==