On Thu, 20 Mar 2014, Jones, Matt wrote: > I am putting together a collection of icinga plugins, and various other tools > including notification scripts and various scripts for working with > configuration files, along the lines of a user contrib collection. For now > they are all written in Python and the notification templates are jinja2/css. > They are tested with Python >2.6 which means RHEL5+ but they designed to work > with Python >2.4. For now I am only testing against the Icinga 1x branch but > soon will spin up an 2x build for further testing. > > I understand C is generally used for good reasons but rapid development and > tweaking is better in my book and all service checks can be compiled into C > using Cython for greater portability. The performance differences I have > seen between the Python and C are not measurable. For now this is source only > but I will create an rpm as well once I get all the checks working. I am > currently poring my collection of perl and shell scripts to python, these are > mainly for adding new hosts, service checks, and working with service/host > groups. > > More details can be found on Github > https://github.com/mattyjones/icinga_plugins Now I found some time to answer. Where I welcome every new Plugin, I don't like the name. The Nagios Plugin API is implemented by a lot of monitoring tools and it is imho wrong to bind the name to a specific monitoring solution. The way the former Nagios Plugins team went is the right way. Monitoring Plugins is a good name and is not implementation specific.
Alex _______________________________________________ icinga-users mailing list icinga-users@lists.icinga.org https://lists.icinga.org/mailman/listinfo/icinga-users
