Skip to content
This repository has been archived by the owner. It is now read-only.
Switch branches/tags

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

Build Status

Icinga 1.x

Icinga Logo

Table of Contents

  1. About
  2. License
  3. Installation
  4. Documentation
  5. Support
  6. Development and Contributions


Icinga 1.x began as a fork of Nagios and is backward compatible. So, Nagios configurations, plugins and addons can all be used with Icinga 1.x. Though Icinga 1.x retains all the existing features of its predecessor, it builds on them to add many long awaited patches and features requested by the user community.

Icinga is an enterprise grade open source monitoring system which keeps watch over a network and any conceivable network resource, notifies the user of errors and recoveries, and generates performance data for reporting. Scalable and extensible, Icinga can monitor complex, large environments across dispersed locations. Icinga is licensed under GPL V2 and is free to use, distribute and modify.

Icinga 2 is the new monitoring core flagship and actively developed. Icinga 1.x receives security and bug fixes only.

Please checkout for more details.


Icinga 1 and the Icinga 1 documentation are licensed under the terms of the GNU General Public License Version 2, you will find a copy of this license in the LICENSE file included in the source package.


Read the INSTALLING file for more information about how to install it.


The documentation is located in the html/doc/ directory. The latest documentation is also available on


Check the project website at for status updates. Join the community channels for questions or ask an Icinga partner for professional support.


The Git repository is located on GitHub.

Icinga 1 is written in C and can be built on Linux/Unix.


There are many ways to contribute to Icinga -- whether it be sending patches, testing, reporting bugs, or reviewing and updating the documentation. Every contribution is appreciated!

Read the contributing section and get familiar with the code.

Pull requests on GitHub are preferred.


Basic unit test coverage is provided by running make test during package builds.

Snapshot packages from the laster development branch are available inside the package repository.