90429 Nürnberg, de
Icinga announces Release of Icinga version 2.11
After many hard days' work the Icinga company is proud to announce the official release of Icinga 2, version 2.11. The new version includes improvements for performance, stability and scalability. The results of the Release Candidate phase that Icinga started in July are now incorporated.
On their way to 2.11 the Icinga developers evaluated new libraries and programming techniques in order to replace the entire code base for the network stack operations in Icinga. The most noticeable change is that Icinga’s distributed cluster operates more stable now. Aside from the rather visible fixes, multiple major and minor changes have been applied to improve the code base for the next years.
The main improvements of Icinga 2.11:
Rewritten Network Stack | Recent times have shown problems with hanging TLS connections, stalled HTTP requests and resource consuming operations with the Icinga network stack. The Icinga developers thus rewrote the network stack based on the well-known and tested Boost library.
Improved Cluster Sync | Icinga 2.11 adds a long-wanted feature to the cluster config sync: Staging for received configuration. This new feature avoids deploying broken configuration directly into production.
Self-Healing & Debugging Docs | In the past, it has happened that downtimes were missing after restart. Icinga 2.11 comes with improved storage for created objects during runtime and heals itself whenever things don’t turn out well. Troubleshooting docs help users during debugging sessions.
High Availability for Features | When enabling features like Graphite or Elasticsearch users can now set the setting enable_ha=true on both sides. The feature will then run only on one node and the other will take over in the case of failure.
Enhanced Core | The JSON library has been replaced and modernized for full UTF8 support. This comes in preparation for the IcingaDB backend and also solves possible crashes on GitHub.
Notifications which would be triggered during the reload phase are now properly sent. Furthermore, when a host/service is still NOT-OK after a downtime ends, a problem notification is sent immediately.
Improved Reload Handling | With the new reload handling the Icinga company creates the foundation for reliable (Docker) containers for Icinga 2. Additionally, this change prevents unwanted notifications during restarts and reloads.
Various small enhancements | All_services for the schedule-downtime host action, on-demand CSR signing CLI tools, getenv() as DSL function and much more.
Icinga 2.11 comes with an extensive upgrading documentation. There are many improvements for service monitoring, distributed monitoring, features, technical concepts, development and the upgrading chapter.
More information in the Icinga Blog and in the Changelog
The use of information published here for personal information and editorial processing is generally free of charge. Please clarify any copyright issues with the stated publisher before further use. In the event of publication, please send a specimen copy to email@example.com.