2.2 Setup analysis
Nagios configuration may look overly complicated at first glance; even the documentation warns that Nagios is quite powerful and flexible, but it can take a lot of work to get it configured just the way you’d like . Anyway, don’t despair! For the first tests, you can start by tweaking the sample configuration files contained in the /usr/local/share/examples/nagios/ directory, customizing them to your needs.
- comments start with a “#” character and span to the end of the line;
- variable brands need begin in the very beginning of the line (we.e. zero indentation acceptance);
- varying labels try circumstances delicate;
- no spaces are allowed around the “=” sign.
Arrangement relates to form several variables about the monitoring daemon, the new CGIs and, obviously https://datingmentor.org/portuguese-dating/, the brand new computers and services we would like to monitor. All this info is pass on among several files: we are going to today take a look at her or him one by one.
2.dos.step 1 An element of the arrangement document
The overall behaviour of the Nagios daemon is determined by the directives included in the main configuration file, /var/www/etc/nagios/nagios.cfg. Though this file contains several dozens of parameters, for most of them the default value is the most reasonable option and you will probably want to care about only very few of them (usually cfg_file, cfg_dir and admin_email). In any case, you can find a detailed description of each and every parameter in the official documentation.
dos.dos.dos The resource document
The allows you to assign values to the user-definable macros “$Representative letter $” (where n is a number between 1 and 32 inclusive). Basically, in Nagios, macros are variables (starting and ending with a dollar sign, “$“) that you can insert into command definitions and that will get expanded to the appropriate value immediately prior to the execution of the command. User-establishd macros (and the several other macros Nagios makes available) allow you to keep command definitions generic and simple (see the next chapter for some examples).
User-defined macros are normally used to store recurring items in command definitions (like directory paths) and sensitive information (like usernames and passwords). It is recommended that you set restrictive permissions (600) on the resource file(s) in order to keep sensitive information protected.
The next thing is configuring target studies, that’s probably the trickiest part of the configuration. We are going to therefore input next chapter entirely to that particular thing.
step 3.0 Target studies arrangement
Now it is time to give Nagios things to continue tabs to your. For this reason, we have to have it with advice on the:
- when and how to perform monitors and you may send announcements;
- exactly who so you can notify;
- and this computers and you may functions to monitor.
All this information is represented by means of , which are defined by a set of “define” , enclosed in curly braces and containing a variable number of newline-separated , in keyword/value form. Keywords are separated from values by whitespace and multiple values can be separated by commas; indentation within statements is allowed.
Object definitions can be split into any number of files: just remember to list them all in the main configuration file by using the cfg_file and/or cfg_dir directives.
3.step one Timeperiod definition
The timeperiod statement allows you to specify, for each day of the week, one or more time slots in which to run certain checks and/or notify certain people. Time intervals can’t span across midnight and excluded days are simply omitted.
In the following example, all the timeperiod definitions are grouped together in a file named timeperiods.cfg stored in the /var/www/etc/nagios/ directory.
step 3.2 Order definition
The next step is to tell Nagios how to perform the various checks and send out notifications; this is accomplished by defining multiple command objects specifying the actual commands for Nagios to run.