2.dos Setup evaluation
Nagios configuration may look overly complicated at first glance; even the documentation warns that Nagios is quite powerful and flexible, but it can take list of black hookup apps 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 names need certainly to start at the start of the range (we.e. no indentation anticipate);
- variable brands was circumstances sensitive and painful;
- no spaces are allowed around the “=” sign.
Configuration comes to mode several parameters regarding keeping track of daemon, the CGIs and, obviously, the fresh new machines and qualities we would like to screen. All of this data is spread one of numerous documents: we will now consider them one at a time.
2.dos.step 1 A portion of the setup file
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_current email address). In any case, you can find a detailed description of each and every parameter in the official documentation.
dos.2.2 The brand new capital file
The allows you to assign values to the user-definable macros “$Associate n $” (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-determined 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 target study, which is possibly the trickiest an element of the setting. We’ll ergo input next part completely to that particular thing.
step 3.0 Target analysis setting
Now it is the right time to share with Nagios what things to continue tabs to the. Thus, we have to have they with advice regarding the:
- when and how to would monitors and you can send out notifications;
- whom to alert;
- and that machines and you will attributes observe.
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_document and/or cfg_dir directives.
step three.1 Timeperiod meaning
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 three.2 Demand 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.
Recent Comments