33ef1cf751
The recursion depth limit added to JsonDecode() in 2.16.2 gave the C++
function a second parameter with a default value. Function pointers do not
carry default arguments, so the DSL function binding deduced an arity of 2
via boost::function_types::function_arity and required two arguments. As a
result `Json.decode("...")` failed with "Too few arguments for function",
an undocumented breaking change in a patch release.
Wrap JsonDecode() in a single-argument shim (mirroring the existing
JsonEncodeShim) so the registered function keeps its one-parameter contract
while still applying the default depth limit internally.
refs #10913
(cherry picked from commit
|
||
|---|---|---|
| .github | ||
| agent | ||
| choco | ||
| cmake | ||
| doc | ||
| etc | ||
| icinga-app | ||
| icinga-installer | ||
| itl | ||
| lib | ||
| plugins | ||
| test | ||
| third-party | ||
| tools | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| AUTHORS | ||
| CHANGELOG.md | ||
| CMakeLists.txt | ||
| config.h.cmake | ||
| Containerfile | ||
| CONTRIBUTING.md | ||
| icinga-spec-version.h.cmake | ||
| icinga-version.h.cmake | ||
| ICINGA2_VERSION | ||
| LICENSE.md | ||
| mkdocs.yml | ||
| NEWS | ||
| publiccode.yml | ||
| README.md | ||
Icinga 2
Table of Contents
About
Icinga is a monitoring system which checks the availability of your network resources, notifies users of outages, and generates performance data for reporting.
Scalable and extensible, Icinga can monitor large, complex environments across multiple locations.
Icinga 2 is the monitoring server and requires Icinga Web 2 on top in your Icinga Stack. The configuration can be easily managed with either the Icinga Director, config management tools or plain text within the Icinga DSL.
Installation
- Installation
- Monitoring Basics
- Configuration
- Distributed Monitoring
- Addons, Integrations and Features
- Troubleshooting
- Upgrading
Once Icinga Server and Web are running in your distributed environment, make sure to check out the many Icinga modules for even better monitoring.
Documentation
The documentation is available on icinga.com/docs.
Support
Check the project website for status updates. Join the community channels for questions or ask an Icinga partner for professional support.
License
Icinga 2 and the Icinga 2 documentation are licensed under the terms of the GNU
General Public License Version 3 or later, you will find a copy of this license in the
LICENSE.md file included in the source package.
In addition, as a special exception, the copyright holders give permission to link the code of portions of this program with the OpenSSL library under certain conditions as described in each individual source file, and distribute linked combinations including the two.
You must obey the GNU General Public License in all respects for all of the code used other than OpenSSL. If you modify file(s) with this exception, you may extend this exception to your version of the file(s), but you are not obligated to do so. If you do not wish to do so, delete this exception statement from your version. If you delete this exception statement from all source files in the program, then also delete it here.
Note
Historically, Icinga 2 has been licensed under the GNU General Public License Version 2 or later. However, due to newly introduced dependencies licensed under the Apache License 2.0 (which is not compatible with GPLv2), we have decided to upgrade the license of Icinga 2 to GPLv3+, effective from version
v2.16.0onwards. All versions prior tov2.16.0and all existing source code files remain licensed under GPLv2+ (see the license information in those files).Also, the OpenSSL linking exception is only relevant for OpenSSL 1.x. OpenSSL >= 3.0 is licensed under the Apache License version 2.0, which is compatible with GPLv3 and no longer requires an exception.
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.
If you are a packager, please read the development chapter for more details.
Security Issues
For reporting security issues please visit this page.