Frequently Asked Questions

And their answers

If you have any questions, ideas or suggestions which are not covered below, please do not hesitate to contact us. Icinga is about active and open communication.

How to register an Icinga account

Some sections on * require a valid login (for reporting a bug on, or editing an article on In order to keep you relaxed, you’ll only need to register one account though – navigate to the accounts page, fill out all required fields, solve the captcha. Then check your email inbox and activate your account. Look into the spam/junk folder too if you cannot find it.

How to report a bug or feature request

To get started, you need to register an Icinga account and then log into the development tracker. Choose the relevant project and click “New Issue” (or as per your locale). Give your new issue a descriptive subject and explain your feature request or problem.

Please include every little detail, be it package versions, configurations, logs or screenshots to support your bug report or feature request. That will help developers to analyze, reproduce, fix & implement patches or new features faster.


What license does Icinga use?

All Icinga software is open source and licensed under GPL version 2 (Icinga Web 1 under GPLv3). So it is free (as in beer and as in speech) to use, distribute and modify.

Is Icinga compatible to Nagios?

YES! The Icinga project seeks to remain compatible with Nagios as long as possible. Take a look at some differences and learn more about migration from Nagios to Icinga.

What does the name Icinga mean? How is it pronounced?

Icinga is a Zulu word meaning ‘it looks for’, ‘it browses’, ‘it examines’. As far as we can tell, it is pronounced with one of the famous Zulu click consonants that require some practice. So the best answer probably is: You can pronounce it any way you like. This is how we do it: “Icinga

What is Icinga 2

Icinga 2 is a network monitoring system and parallel development branch to Icinga 1. It is a core framework replacement (no GUI) that seeks build on the success of Icinga 1 and deal with shortcomings inherited from Nagios as a fork. Where “Icinga” is mentioned in blog posts prior to October 25th, 2012, we are usually referring to Icinga 1.


What is a fork?

A fork happens, when someone takes a copy of source code from a software package, e.g. Nagios and starts independent development based on it – thus creating a new and distinct piece of software.

Free or open source software may be forked with no prior permission, per the definitions of “free software” (“Freedom 3: The freedom to improve the program, and release your improvements to the public, so that the whole community benefits”) and “open source” (“3. Derived Works: redistribution of modifications must be allowed. (To allow legal sharing and to permit new features or repairs.)”).

Examples of successful forks are Joomla (forked from Mambo), X.Org (forked from XFree86).or MariaDB (forked from MySQL).

See Wikipedia for more information.

What's the difference between Icinga and Nagios?

Over time, Icinga has implemented hundreds of patches, bug fixes and new features in response to community requests. These have largely been implemented in Icinga 1 (Nagios fork), Icinga Classic and Icinga Web, as well as Icinga Reports.

As of October 2012 we have been working steadily on a new monitoring solution Icinga 2  (written from scratch) and more recently our next generation interface, Icinga Web 2.

For more information: Icinga vs. Nagios – What’s the difference?

For more technical details: Icinga vs. Nagios – A Developer’s Comparison