[Pkg-nagios-devel] Bug#734453: Bug#734453: Bug#734453: nagios3: Please package v.4

Michael Friedrich michael.friedrich at gmail.com
Tue Jan 7 19:16:48 UTC 2014

On 07.01.2014 13:18, Alexander Wirt wrote:
> On Tue, 07 Jan 2014, Tim Wootton wrote:
>> On 07/01/14 11:08, Alexander Wirt wrote:
>>> I won't do this. Nagios is a dead horse and is far away from opensource this
>>> days. I'll support nagios3 as long as possible and icinga(1|2) and naemon.
>> Thanks for the info Alex. Will icinga be using the 4.x style "core
>> workers"?  I understand there are
>> considerable performance gains to be had there & that was my main
>> motivation in asking for 4.02
> icinga1 probably not,

I've been following Andreas Ericsson's development on Nagios 4 closely 
and ported the code for prototyping a year ago or something. There's 
plenty of new stuff, lots of hidden bugs, missing features, etc so that 
I have given up on that a while ago. It causes more time & ressources to 
understand and port foreign code, rather than implementing your very own 
ideas. Though, I had core workers in mind even before I've seen them in 
Nagios svn.

There are still ways to scale Icinga 1.x with the help of addons, but 
given the horrible code base Icinga inherited from Nagios as a fork, 
there was a decision made in terms of ressources and we are now happy to 
focus not only on scalability with Icinga 2, but also with a sound base 
for developers and future extensions & features (such as recurring 
downtimes in 0.0.6). Current task - work hard towards 2.0.0 final.

Icinga 1.x won't get those workers, unless someone steps in, ports the 
code & maintains it for the time being. Probably the last thing is the 
one which hurts the most. Note: This is my personal opinion as currently 
assigned lead core dev.

> icinga2 has a completly different model and should be
> more perfomant.

It is. In terms of scalability, one could consider the native cluster 
stack implemented for load distribution on checks. But our test lab 
would say that providing Icinga 2 some hardware, and it will scale on a 
standalone box with say 100k checks. Still, the new configuration format 
might be a migration challenge, but there's a migration script, and 
config addons may adopt it soon-ish (as already happened to LConf, or 
maybe later natively in IcingaWeb2). Markus Frosch is already working on 
Debian packages which are probably uploaded to unstable once they are 
revised and given the ok. Until then, try the vagrant demo box ;-)

> Naemon is a fork from nagios4 and took its main developer
> with him, so that should work.

Let the presentation from OSMC 2013 speak for itsself.


DI (FH) Michael Friedrich

mail:     michael.friedrich at gmail.com
twitter:  https://twitter.com/dnsmichi
jabber:   dnsmichi at jabber.ccc.de
irc:      irc.freenode.net/icinga dnsmichi

icinga open source monitoring
position: lead core developer
url:      https://www.icinga.org

More information about the Pkg-nagios-devel mailing list