dos.2 Setting assessment

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;
• changeable brands must initiate at the start of the range (we.elizabeth. zero indentation anticipate);
• adjustable names is instance sensitive and painful;
• no spaces are allowed around the “=” sign.

Setting involves function numerous variables regarding the overseeing daemon, the fresh CGIs and you will, of course, the machines and you will attributes we would like to display. All this information is bequeath certainly one of numerous records: we are going to now examine her or him one-by-one.

dos.dos.step 1 The main arrangement 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_email). In any case, you can find a detailed description of each and every parameter in the official documentation.

dos.2.2 The funding document

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-described 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 object studies, that’s even the trickiest the main arrangement. We’re going to for this reason devote the second part entirely to that topic.

step three.0 Object data setup

Now it is the right time to share with Nagios what to remain tabs towards. For this reason, we must likewise have it with advice regarding the:

• whenever and how to perform checks and you will send out notifications;
• exactly who so you’re able to notify;
• which machines and you will features 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_document and/or cfg_dir directives.

3.1 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.

3.dos Order meaning

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.