Monthly Archives: January 2014

Introducing the Nagios-Plugins Security Team Lead — Spenser Reinhardt

We would like to introduce the second team member in charge of maintaining the Nagios-Plugins Project — Spenser Reinhardt.  Spenser has been named the Nagios-Plugins Security Team Lead and has already begun contributing to critical bug fixes and plugin improvements.

Like our Project Team Lead Andy Brist, we also subjected Spenser to a rigorous interview in order to give community members an inside look at the latest addition to the Nagios-Plugins Development Team.  View the interview below and get to know the new Nagios-Plugins Security Lead — Spenser Reinhardt:

Introducing the Nagios-Plugins Team Lead — Andy Brist

As you may have heard, there have been some changes to the Nagios-Plugins Development Team.  The greatest of which comes in the form of new project maintainers.  Both Andy Brist and Spencer Reinhardt will be heading the Nagios Plugins project moving forward and have the knowledge and expertise to do so.

We thought that the best way to introduce the new team members to the community was to subject them to a grueling interview process.  This short video introduces Andy Brist, the New Nagios-Plugins Team Lead, and sheds some light on his Nagios credentials as well as his personal interests.

Uncomfortable Info On The Plugin Team Changes

Change isn’t always easy, but sometimes its necessary. Recently, the Nagios Plugins website and team have undergone some changes, and for good reason.  There have been a few people who have caused a stir about the changes, and there’s been some misunderstanding as to the reasons behind those changes, so we thought we’d share some relevant info with the community.

The changes were made because there was an organized effort by some individuals to undermine the project and move people to another solution.  Some of the previous team members decided “recently” to switch development to a new project after we started to employ some changes.  Except their decision to switch wasn’t recent – they made it months ago.  This can be evidenced in part by their Git commits which show them beginning to make a switch as early as last September.  You’ll notice the screenshot below showing a change that was made to start transitioning the Nagios plugins project to a new domain and project (original URL).


In addition to this and other similar changes, some of the previous team members started promoting competitors of Nagios in an effort to move people away from the project.  Our attempts to get a response from the previous team lead on multiple occasions to clarify what was happening was met with silence.  So we acted.

We stepped in to prevent these individuals from subverting the project.  We’ll do what we need to do to preserve the various Nagios projects from people and companies with ulterior motives.

Its been an interesting study to watch what some people try to get away with in order to promote their ulterior motives.  One example of this is the outright lies and FUD promoted by Michael Friedrich, as can be seen in his calls for the Fedora/RedHat maintainers to automatically switch Nagios users to a competing solution.  Not surprising that Michael works for Netways GmbH – the same company that recently wrongfully filed Nagios trademark and domain registrations in secret in order to undermine Nagios and the community.  Only after we shamed them by publicly disclosing the details, did Netways finally return the trademarks and domains they were leveraging.  I think its safe to say that words like honesty, integrity, and ethics aren’t valued or even understood by Netways and its employees.

We understand that it can get uncomfortable for individuals when evidence is presented that shows they acted less than honorably.  We at Nagios believe that who you work with is just as important as what it is that you’re working on.  We will always chose to work with individuals with high ethical standards and a great attitude.  If you have skills, but you don’t have values, you won’t be on our team.  Period.

– Ethan Galstad, Nagios Founder and Defender

Nagios Plugins Mailing Lists Moved To New Server

As part of our efforts to improve the Nagios Plugins project, we’ve moved from using the old SourceForge mailing lists for the Nagios Plugins project to a new dedicated list server.  The new mailing list server runs Mailman (which is what the old SourceForge lists ran), so you should find it familiar.  If you were a subscriber to one of the old Nagios Plugins mailing lists, you should have been automatically subscribed to the appropriate new list(s).

The main email list addresses for the Nagios plugins projects are now as follows:

We weren’t able to migrate list membership preferences from SourceForge, so if you prefer a digest subscription or other options, you’ll have to manage your subscription by visiting:

The Nagios Plugins team, as well as the support staff at Nagios Enterprises will be helping to provide support for anyone who has problems or questions related to compiling, installing, or using the plugins

Questions for the Community

I am excited to be the new lead for the nagios-plugins project and look forward to working with the community and other plugin developers to better the project.  Even though we have started to fix some low hanging issues, we have larger plans for the project overall.  Once we finish setting up the automated build and testing servers, the team will open the project up for new plugin submissions.  I have a few questions for the community below, which you can respond to through the mailing lists (Nagiosplugin-commits, Nagiosplugin-devel, Nagiosplugin-help), forum, or directly in the comments below.

1. What distributions (if any) have had problems with building in the past and should be targeted for the automated tests?

2. Are there any plugins that you wish were included in the official nagios-plugins package? (We will be perusing the exchange for popular abandoned gpl perl/c plugins, but user input and submissions are always appreciated)

-Andy Brist