Nagios was the undisputed king of open source monitoring for a decade. Built by Ethan Galstad starting in 1999, it became the default way to monitor servers, networks, and services across the IT industry. But Galstad ran Nagios like a personal fiefdom, and by the late 2000s, the kingdom was rotting from within.

The core problem was simple: Nagios development was a one-man show. Galstad controlled all commits, and community-submitted patches piled up for months — sometimes years — without being reviewed or merged. There was a two-year gap between Nagios Core releases. Community developers who had written significant improvements found their work gathering dust in a bug tracker that felt more like a black hole. Meanwhile, Galstad was increasingly focused on Nagios Enterprises, the commercial arm, while the open source project stagnated.

In May 2009, a group of prominent Nagios community developers and addon creators said enough. They forked Nagios as Icinga (the Zulu word for 'it searches' or 'it examines') and announced their intention to build a truly community-led monitoring project. The fork started as a straightforward improvement of the Nagios Core codebase, adding the database flexibility and modern web interface that the community had been begging for.

Galstad's response was disappointment rather than anger — he admitted to the development bottleneck but was hurt that the Icinga team hadn't approached him first. The Nagios community split along predictable lines, with addon developers and system administrators taking sides in what Free Software Magazine called 'one of the most heated forks in free software.'

The real vindication for Icinga came with Icinga 2, released in 2014 as a complete ground-up rewrite. Rather than continuing to polish the Nagios codebase, the team built a modern monitoring system with a distributed architecture, a proper API, native cluster support, and a configuration language that didn't make sysadmins weep. It was the product that Nagios should have become if it had accepted community input.

Icinga demonstrated that a benevolent dictator model only works if the dictator is actually benevolent and engaged. By embracing community development, Icinga eventually surpassed Nagios in features, architecture, and community vitality. Icinga 2's modern architecture — with native clustering, API-first design, and proper configuration management — represented the monitoring tool that Nagios Core never became.

The fork also reshaped the monitoring landscape. While both projects continue to exist, Icinga's success (along with the rise of Prometheus, Grafana, and other modern tools) eroded Nagios's once-dominant market position. Nagios Enterprises pivoted hard toward commercial products, while Icinga maintained its open source ethos with commercial support from NETWAYS.