dos.2 Setting review
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;
- adjustable names must begin in the beginning of the range (we.e. no indentation desired);
- variable brands is actually instance delicate;
- no spaces are allowed around the "=" sign.
Setting involves mode numerous variables concerning the keeping track of daemon, the latest CGIs and, naturally, new machines and you may attributes we wish to screen. All of this information is give certainly one of several data: we shall today consider her or him one by one.
dos.2.step one An element of the configuration 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.
2.dos.2 The brand new resource file
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 demand definitions and that will get expanded to the appropriate value immediately prior to the execution of the command. User-explaind 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 step is configuring object study, that's even the trickiest a portion of the configuration. We'll ergo devote another section entirely compared to that procedure.
step 3.0 Target studies setting
Now it's time to share with Nagios what to keep tabs to the. For this reason, we have to also have it with information on the:
- whenever and ways to perform monitors and you will distribute announcements;
- just who to help you notify;
- and therefore servers 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.
step 3.step 1 Timeperiod definition
The timeperiod statement allows you escort reviews North Charleston SC 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 three.2 Command 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.