Nagios core configurations quickly become huge. It is impossible to keep an overview of every configuration.
Using xls2nag.py
you can keep your entire configuration in a single excel file.
The only object type you can't convert to excel is the timeperiod
object since the directives are not consistent enought to convert to excel
xls2nag.py
opens the excel and generates a new config file per sheet, using the name of the sheet as the name of the config file
every row in the excel defines an entire object as described in the nagios definition pages
An example of how commands are configured in excel. This sheet is called commands
in excel looks like this:
xls2nag.py
will generate the config file from each sheet. This file is called commands.cfg
and will look like this:
In this case, my 83 lines command sheet convert into 546 lines of nagios configuration file, and this is quite ok because there are only a few directives in these objects. For comparison, my 336 lines of services converts to a 2227 line sequencial config file. The advantage of the excel is that you have a way better overview and can edit multiple objects at the same time.
Here is a comparable example of some service templates i defined in excel (for clarity i hid some of the columns):
and what the generated nagios configuration looks like.