We create a lot of Nagios installations for our own systems over, for customer systems which we manage and as a service over at Open Solutions. We’ve written a lot of custom Nagios plugins over the years as part of this process.
We are now making a concerted effort to find them, clean them, maintain them centrally and release them for the good of others.
To that end, we have created a repository on GitHub for the task with a detailed readme file:
They main goal of Nagios plugins that we write and release are:
- BSD (or BSD like) license so you can hack away to wield into something that may be more suitable for your own environment;
- scalable in that if we are polling power supply units (PSUs) in a Cisco switch then it should not matter if there is one or a hundred – the script should handle them all;
- WARNINGs are designed for email notifications during working hours; CRITICAL means an out of hours text / SMS message;
- each script should be an independant unit with no dependancies on each other or unusual Perl module requirements;
- the scripts should all be run with theÂ
--verbose on new kit. This will provide an inventory of what it finds as well as show anything that is being skipped. OIDs searched for by the script but reported as not supported on the target device should really be skipped via variousÂ--skip-xxx options. - useful help available viaÂ
--help orÂ-?