ed2ebdf0d0
Use case: a reader subscribes to config changes. As they happen rarely, chances are good that the connection will time out in the meantime. Now, a reconnect is easy - but you wouldn't know whether you missed any config changes. So you are required to issue a new sync to be on the safe side. Given a 60sec connection timeout (think: SSL layer, firewalls etc) when no traffic happens this would be too expensive. Some kind of a heartbeat available for subscription would allow subscribers to artificially keep the connection alive. As a first simple solution to this I'd suggest to publish CIB data, that might be useful anyways. refs #4991 fixes #5098 Signed-off-by: Michael Friedrich <michael.friedrich@icinga.com>
Icinga 2
Table of Contents
About
Icinga 2 is an open source monitoring system which checks the availability of your network resources, notifies users of outages, and generates performance data for reporting.
Scalable and extensible, Icinga 2 can monitor large, complex environments across multiple locations.
Icinga 2 as monitoring core works best with Icinga Web 2 as web interface.
More information can be found at www.icinga.com and inside the documentation.
License
Icinga 2 and the Icinga 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
Read the INSTALL.md file for more information about how to install it.
Documentation
The documentation is located in the doc/ directory. The latest documentation is also available on https://docs.icinga.com
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.
Development
The Git repository is located on GitHub.
Icinga 2 is written in C++ and can be built on Linux/Unix and Windows. Read more about development builds in the INSTALL.md file.
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 read the contributing section first. Then you should have a look at the roadmap and remaining open issues.
Pick issues you want to help resolve, fork the repository on GitHub and send a pull request with your changes. Thanks for your contribution!
Testing
Basic unit test coverage is provided by running make test during package builds.
Read the INSTALL.md file for more information about development builds.
Snapshot packages from the laster development branch are available inside the package repository.
You can help test-drive the latest Icinga 2 snapshot packages inside the Icinga 2 Vagrant boxes.