A lightweight and extensible web interface to keep an eye on your environment. Analyse problems and act on them.
Go to file
Alexander A. Klimov fc1f6e13ab Drop PHP 5.3 support 2018-05-07 11:36:54 +02:00
.github
.puppet
application Drop PHP 5.3 support 2018-05-07 11:36:54 +02:00
bin
doc
etc
library Drop PHP 5.3 support 2018-05-07 11:36:54 +02:00
modules Drop PHP 5.3 support 2018-05-07 11:36:54 +02:00
packages
public Merge pull request #3425 from Icinga/fix/avoid-unnecessary-search-requests-3348 2018-04-25 03:08:47 -04:00
test Drop obsolete Icinga\Web\Menu classes 2018-04-27 14:28:20 +02:00
.gitattributes
.gitignore
.mailmap
.travis.yml Drop PHP 5.3 support 2018-05-07 11:36:54 +02:00
AUTHORS Update AUTHORS 2018-04-25 12:55:52 +02:00
CHANGELOG.md Update CHANGELOG.md 2018-04-25 14:05:08 +02:00
CONTRIBUTING.md
COPYING
README.md
RELEASE.md
VERSION Update VERSION 2018-04-27 10:23:20 +02:00
Vagrantfile
icingaweb2.ruleset.xml
phpcs.xml

README.md

Icinga Web 2

Build Status Github Tag

Icinga Logo

  1. About
  2. License
  3. Installation
  4. Documentation
  5. Support
  6. Contributing

About

Icinga Web 2 is the next generation open source monitoring web interface, framework and command-line interface developed by the Icinga Project, supporting Icinga 2, Icinga Core and any other monitoring backend compatible with the IDO database.

Icinga Web 2 with Graphite Icinga Web 2 Sidebar Collapsed

License

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

Installation

For installing Icinga Web 2 please read doc/02-Installation.md.

Documentation

The documentation is located in the doc/ directory.

Support

Check the project website at https://www.icinga.com for status updates. Join the community channels for questions or ask an Icinga partner for professional support.

Contributing

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!

Please continue reading in the contributing chapter.