The H briefly covers a fork in the Nagios community. "The team behind ICINGA, including Michael Luebben, Hendrik Bäcker and Joerg Linge, all members of the Nagios Community Board, are promising that ICINGA will be fully compatible with the preceding version of Nagios. What they aim to do with ICINGA is to fix long standing bugs, make improvements to database integration and standardise the API for third party add ons. They expect to make the first release of ICINGA code by the end of May and a first stable version is planned for the end of October."
(Log in to post comments)
Nagios forks to ICINGA (The H)
Posted May 6, 2009 21:35 UTC (Wed) by mmcgrath (subscriber, #44906)
[Link]
In Fedora we recently started moving to zabbix for the same reason listed in the link: "frustrated by the lack of a roadmap or progress for Nagios". 3.0 came out and I wondered to myself - "this is what we've all been waiting for?"
Posted May 7, 2009 4:47 UTC (Thu) by sjj (subscriber, #2020)
[Link]
I would be interested in hearing your reasons for selecting zabbix. I'm trying to come up with a plan to run away, er, upgrade several hundred servers from bb.
Is there archived discussion on some mailing list or wiki?
Nagios forks to ICINGA (The H)
Posted May 7, 2009 11:46 UTC (Thu) by Klavs (subscriber, #10563)
[Link]
I also tested zabbix, but the only way to configure it, is via the webinterface and it allowed me to add groups - which where then not added, even though they said it were and so on. This with v1.6.
It felt too none-transparent to me- and I really need to know that the monitoring system is simple(and thus transparent) enough so I know I can trust it.
For that reason I choose Nagios with nagiosgraph spitting out RRD's and then cacti to show the Nagios RRD's and other RRD's (like trafic and IO things) that I don't want Nagios to monitor.
Nagios forks to ICINGA (The H)
Posted May 7, 2009 13:06 UTC (Thu) by mmcgrath (subscriber, #44906)
[Link]
> Is there archived discussion on some mailing list or wiki?
Posted May 13, 2009 4:18 UTC (Wed) by PaulWay (✭ supporter ✭, #45600)
[Link]
I notice that Ethan has posted a couple of articles on the fork on the Nagios Community website (http://community.nagios.org). In them he's basically supportive of the fork, and states several reasons why he thinks it's good for Nagios (it being a sign that the Nagios community wants to get more involved being one).
He also states that he hadn't received any communication from the Icinga project leaders before they went public. It doesn't seem to come as a surprise to Ethan, though - he acknowledges that development was "slowed by some bottlenecks" and doesn't deny that the cause of the fork was a "lack of communication on my part". So I think he acknowledges the problems that may stem from him and Nagios Enterprises and wants to work with the Nagios and Icinga communities.
Personally I'm hoping this goes more in the direction of Compiz Fusion than EGLIBC, and I think the positive attitude that Ethan and the Icinga people will work toward the projects rejoining again in the near future.