For instructions on installing these plugins for use with Nagios, see below. In addition, generic instructions for the GNU toolchain can be found in the
For major changes between releases, read the
For information on detailed changes that have been made or plugins that have been added, read the
Some plugins require that you have additional programs and/or libraries installed on your system before they can be used. Plugins that are dependent on other programs/libraries that are missing are usually not compiled. Read the
REQUIREMENTSfile for more information.
Individual plugins are self-documenting. All plugins that comply with the basic guidelines for development will provide detailed help when invoked with the
You can check for the latest plugins at:
Send an email to firstname.lastname@example.org for assistance. Please include
the OS type and version that you are using. Also, run the plugin with the
-vvv option and provide the resulting version information. Of course,
there may be additional diagnostic information required as well. Use good
Send an email to email@example.com for developer discussions.
For patch submissions and bug reports, please use the appropriate resources at:
If you are using the Git tree, you will need m4, gettext, automake, and autoconf. To start out, run:
For more detail, see the developer guidelines at https://www.nagios-plugins.org/doc/guidelines.html.
Run the configure script to initialize variables and create a Makefile, etc.
./configure --prefix=BASEDIRECTORY --with-cgiurl=SOMEURL
BASEDIRECTORYwith the path of the directory under which Nagios is installed (default is
/usr/local/nagios), and replace
SOMEURLwith the path used to access the Nagios CGIs with a web browser (default is
Compile the plugins with the following command:
Install the compiled plugins and plugin scripts with the following command:
The installation procedure will attempt to place the plugins in a
libexec/subdirectory in the base directory you specified with the
--prefixargument to the configure script.
There are some plugins that require setuid. If you run make install as a non-root user, they will not be installed. To install, switch to root and run:
That's it! If you have any problems or questions, feel free to send an email to firstname.lastname@example.org.
Testing With libtap
The nagios-plugins source includes a perl testing suite. the libtap library and headers are included with the source. Configure with:
Note: "--enable-extra-opts" used to be required as well, but is no longer required as it is a default configure option.
Make and then make test:
make make test
Testing is pseudo intelligent and will try to autodetect which plugins to test. You may need to look at the REQUIREMENTS doc as to what dependencies are required to satisfy the test.
Additionally, default and user supplied (at runtime) testing parameters are saved in the file:
If you need to change any testing parameters, edit them in this file or just remove the line to force the test to re-prompt you for input.
You can redistribute and/or modify this software under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3 of the License, or (at your option) any later version; with the additional exemption that compiling, linking, and/or using OpenSSL is allowed.
This software is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
COPYING file for the complete text of the GNU General Public
License, version 3.
Static Analysis Tools
Coverity is a tool used to statically analyze C\C++ code and determine possible vulnerabilities, bugs, and usage errors. Nagios-Plugins considers these items to be extremely important for proper code coverage and longevity. It should be noted that a "Passed", does not mean that all Coverity reported issues have been resolved, instead that the latest build submitted did not have any newly found issues, and may or may not have eliminated previously found issues. We use several testing processes that end with a submission to Coverity on each successful build. This means that you will often see this badge pending or with new issues found as new features, pull requests, and github issue resolutions submitted in other branches will reflect on the badge displayed on the master branch. However, the master branch and therefore any releases will not be updated without a current clean scan from Coverity. With that said, below you can find the current state of the Nagios-Plugins project per Coverity's view.